-
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
Launch with optimization turned off #424
Conversation
…pport-via-cli # Conflicts: # conf/reflect-config.json
Do I need to do anything special to get the optimization available? I created a pipeline inside a workspace and ran it, but still can't see the lamp. |
I'm assuming you are running the pipeline in Seqera Platform (not in a local dev env) Did the pipeline finish successfully?
Is the lamp icon shown as unavailable or is it not shown at all? |
It can't be ran locally? |
It can, of course. But, given that tower-cli is a public repo, the test should be expected to run against prod so everyone can try it. We can discuss offline the setup for the local instance. |
tested! works fine! |
…pport-via-cli # Conflicts: # src/main/java/io/seqera/tower/cli/commands/runs/DumpCmd.java
Description
Closes #393
This PR adds support for disabling the optimized configuration when launching a pipeline by setting the
--disable-optimization
flag.Guidelines for testing
./tw
with optimization turned off and check that the configuration does NOT contain the optimized parameters.