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

use a remote config in kuberun #2781

Merged
merged 5 commits into from
Apr 14, 2022

Conversation

Lehmann-Fabian
Copy link
Contributor

Using kuberun with remote configs is not yet possible. Therefore, I added the option to use a config file only located in the cluster.

Signed-off-by: Lehmann-Fabian <fabian.lehmann@informatik.hu-berlin.de>
Copy link
Member

@bentsherman bentsherman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me overall. Just a few small things and then we'll be ready to merge:

  • please address my comments below
  • add the new options to the Nextflow kuberun docs
  • confirm that you've tested this feature on your k8s cluster

@@ -248,7 +248,7 @@ class K8sDriverLauncher {
.setProfile(cmd.profile)
.setCmdRun(cmd)

if( !interactive && !pipelineName.startsWith('/') ) {
if( !interactive && !pipelineName.startsWith('/') && !cmd.remoteProfile && !cmd.runRemoteConfig ) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would just checking cmd.runRemoteConfig be sufficient here?

…ith config

Signed-off-by: Lehmann-Fabian <fabian.lehmann@informatik.hu-berlin.de>
Signed-off-by: Lehmann-Fabian <fabian.lehmann@informatik.hu-berlin.de>
@Lehmann-Fabian Lehmann-Fabian force-pushed the remoteProfile branch 2 times, most recently from 7d9b10f to ed1be19 Compare April 11, 2022 15:11
@Lehmann-Fabian
Copy link
Contributor Author

@bentsherman can you please start the checks manually? The CI Pipeline seems not to start automatically.

@bentsherman
Copy link
Member

@pditommaso Can you tell why the CI tests aren't running? I can't trigger them manually. It just says "Waiting for status to be reported", I don't know what that means.

@pditommaso
Copy link
Member

it may be related to this change 6e23e03. @jorgeaguileraseqera any clue?

Lehmann-Fabian added a commit to Lehmann-Fabian/nextflow that referenced this pull request Apr 14, 2022
The PR action is not started automatically: nextflow-io#2781
It seems to be related to nextflow-io@6e23e03
@Lehmann-Fabian
Copy link
Contributor Author

I think this PR should fix it: #2796

Lehmann-Fabian added a commit to Lehmann-Fabian/nextflow that referenced this pull request Apr 14, 2022
The PR action is not started automatically: nextflow-io#2781
It seems to be related to nextflow-io@6e23e03

Signed-off-by: Lehmann-Fabian <fabian.lehmann@informatik.hu-berlin.de>
pditommaso pushed a commit that referenced this pull request Apr 14, 2022
* Start Github Actions also for edited PRs

The PR action is not started automatically: #2781
It seems to be related to 6e23e03

Signed-off-by: Lehmann-Fabian <fabian.lehmann@informatik.hu-berlin.de>
@pditommaso pditommaso merged commit 5485b69 into nextflow-io:master Apr 14, 2022
@pditommaso pditommaso added this to the 22.04.0 milestone Apr 23, 2022
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

Successfully merging this pull request may close these issues.

None yet

3 participants