Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

running the workflow on a local cluster #1

Open
ManuelTgn opened this issue Mar 6, 2023 · 4 comments
Open

running the workflow on a local cluster #1

ManuelTgn opened this issue Mar 6, 2023 · 4 comments

Comments

@ManuelTgn
Copy link

Hi team,

I've been trying to build the workflow on a local cluster, but the build failed returning the following message:

Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':shadowJar'.
> Could not resolve all dependencies for configuration ':runtimeClasspath'.
   > Could not resolve io.krews:krews:0.12.0.
     Required by:
         project :
      > Could not resolve io.krews:krews:0.12.0.
         > Could not get resource 'https://maven.pkg.github.com/weng-lab/krews/io/krews/krews/0.12.0/krews-0.12.0.pom'.
            > Cannot invoke "String.indexOf(int)" because "username" is null

By looking at the code it looks like it is asking for a username and a token to access some virtual environment.
I'm wondering if there is any way the workflow could be run locally

Thanks for your help,
Manuel

@hpratt
Copy link
Member

hpratt commented Mar 14, 2023

Hi Manuel

Sorry for the trouble! Looks like our public-facing package for that Krews version (0.12.0) is not available anymore after JCenter shut down, and unfortunately the GitHub packages version requires a GitHub token to pull.

We'll work on getting the package available somewhere where credentials aren't required. In the meantime you may have success with the following workaround:

(1) clone https://github.com/weng-lab/krews
(2) within the krews directory, run scripts/build.sh and scripts/deploy.sh
(3) within the motif-workflow directory, git pull then try to build again

I'll push an update when we have the latest Krews version somewhere public.

@ManuelTgn
Copy link
Author

Hi team,

I've been trying the workaround you suggested, however it does not work either. It fails while running scripts/build.sh, with the following message:

FAILURE: Build failed with an exception.

* What went wrong:
Could not create service of type ScriptPluginFactory using BuildScopeServices.createScriptPluginFactory().
> Could not create service of type PluginResolutionStrategyInternal using BuildScopeServices.createPluginResolutionStrategy().

I tried to clean Gradle's cache running ./gradlew cleanBuildCache, but I run into the same error.

Thanks,
Manuel

@hpratt
Copy link
Member

hpratt commented Mar 15, 2023

The other thing you can try for the moment is to generate a token to pull from GitHub packages:

(1) create a classic token here with the "read:packages" permission: https://github.com/settings/tokens
(2) go into the motif-workflow directory and run ./gradlew --stop to stop any running gradle daemons
(3) run USERNAME=your-github-username TOKEN=token-generated-above ./gradlew shadowJar to build the workflow

@ManuelTgn
Copy link
Author

The proposed solution worked, the build completed without any failure!
Just a last question, to run the workflow should I modify the config files to point to local files? Is running scripts/run.sh enough to run the workflow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants