-
Notifications
You must be signed in to change notification settings - Fork 9
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
add --launch-container option in launch command #444
add --launch-container option in launch command #444
Conversation
ok, let's sync with @tcrespog for the sdk |
PR to add in sdk |
this SDK PR is not correct, checking with @JaimeSeqLabs to fix it |
SDK pr has been fixed |
@tcrespog is there recent chnages in GoogleBatchPlatform? Tests are failing for it with new tower sdk
|
Yes, in In |
I'm assuming the tests failing here are the native ones. |
Was the |
I am not sure, how to test it? |
|
This option allows you to change the nextflow launcher used by Platform when running a workflow. Use for example You may want to use https://cloud.stage-seqera.io/ for sake of simplicity and run this "workflow" https://github.com/pditommaso/nf-sleep When running it should show (or use your local platform as Jaime is suggesting) |
Co-authored-by: Paolo Di Tommaso <[email protected]>
Excellent. |
This PR will add --launch-container option in launch command