Closed tiborsimko closed 3 years ago
BTW, running docker to verify steps is good, but that could be another CI check, so that we separate "Validate workflows" (using r-client
) and "Run workflow" (in serial mode, using Docker, which is good for testing containers and source commands in a "vanilla" mode, without having access to REANA cluster.
If we want to get extra fancy, we could introduce separate "Run workflow" tests with running on naked CWL/Yadage/Serial-on-Docker/Snakemake environment, using the usual out-of-REANA instructions that we document there, i.e. mkdir snakemake-local-run
etc.
Advantage: we would catch automatically when demo examples cannot be run outside REANA anymore.
r-d-helloworld
migrated: https://github.com/reanahub/reana-demo-helloworld/pull/55r-d-root6-roofit
and r-d-worldpopulation
still missingThe r-d-helloworld
runs one check only, called build
, and the various tests are performed there. What about running these tests separately? In this way we'll see faster which one failed, and the checks would be more appropriately called than only "build". Something like;
I've introduced a composite action to avoid code repetition.
Right now it's hosted in the same repo, but we should consider creating a repo called reana-actions
or similar to host actions and use them across all our repos. E.g. All the demos would benefit from the local-run
composite action that I've created in the r-d-helloworld
.
We have many REANA spec files now:
But in the GitHub CI "Validate workflow" test, we are using only Yadage:
We should plug validation of all the workflows.
P.S. Some demo examples use
reana-client
for validation.P.S. The same applies to
reana-demo-root6-roofit
andreana-demo-worldpopulation
.