Use nextflow to distribute Jenkins CI over Sherlock nodes #247
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows us to test that the workflow pipeline (
runscripts/workflow.py
) works properly on Sherlock and means we can keep the resource requirements of the long-running Jenkins job to a minimum. One core should be enough togit pull
the latest changes, set up the environment, and launch the Nextflow orchestrator which will submit ParCa/sim/analysis jobs to the cluster.