reana
reana copied to clipboard
reana-dev run-ci: --submit-only --check-only
Current behaviour
Here is a typical CI run invocation:
$ reana-dev run-ci -m /var/reana:/var/reana -c r-d-r-roofit --admin-email john.doe@exampleorg --admin-password mysecretpassword
This command always uses some demo example to make sure that the CI build and deployment succeeds well.
The demo example is usually running all CWL, Serial, Snakemake, Yadage workflows in sequential order. This may take time.
Expected behaviour
Similarly to #697, it may be useful to allow for parallel running of demo examples. Note that this is already possible using:
$ reana-dev run-example -c r-d-r-roofit --submit-only
$ # ... wait some minutes
$ reana-dev run-example -c r-d-r-roofit --check-only
The idea of this issue would be to allow specifying --submit-only
to run-ci
command, so that the cluster would be build and deployed and tested as fast as possible.
We could simply add --submit-only
option and leave --check-only
out, so that the interaction would be:
$ reana-dev run-ci -m /var/reana:/var/reana -c r-d-r-roofit --admin-email john.doe@exampleorg --admin-password mysecretpassword --submit-only
$ # ... wait some minutes
$ reana-dev run-example -c r-d-r-roofit --check-only
Alternatively, run-ci
could also have the --check-only
option, in which case it would not build anything, only check the results. In this way, run-example
and run-ci
commands would behave similarly as far as sequential vs parallel demo submission and result checking is concerned.
I think I would prefer the latter option.