umccrise v2.3.1 tool def

[pdiakumis]

Adding umccrise v2.3.1 CWL.
I've added the --1 suffix since I used the --0 suffix in dev with the rc Docker tags (hope that's okay!).

• Step 1:

cwl-ica create-tool-from-template \
  --tool-name umccrise \
  --tool-version 2.3.1--1 \
  --username "Peter Diakumis"

• Step 2:

cwl-ica tool-validate \
  --tool-path tools/umccrise/2.3.1--1/umccrise__2.3.1--1.cwl

• Step 3:

cwl-ica tool-init \
  --tool-path tools/umccrise/2.3.1--1/umccrise__2.3.1--1.cwl --projects "development_workflows,production_workflows"

Extra notes (for my own sake):

There are now new umccrise entries in config/project.yaml under development_workflows and production_workflows, and a new umccrise entry in config/tool.yaml.
I suspect the __GIT_COMMIT_ID__ under the production_workflows gets updated by the PR bot.
The CWL version has also been copied to staging and development from what I can see, probably via Step 3 above.

[skanwal]

LGTM - you're on board with the process ;)

[pdiakumis]

Merging - 2.3.1--1--9344851 added to prod 👍

[alexiswl]

Well done Peter! Well documented, and this method is totally fine. In the past I've just used the RC tag on --0 until we've got an actual release and then just replaced the docker tag in the original CWL definition. cwl-ica tool-sync to then overwrite the definition in the development_workflows project. We'd then initialise the tool in the production_workflows project with cwl-ica add-tool-to-project subcommand once we have the proper docker tag.

[victorskl]

Portal Release - Ocicat: Update umccrise for DRAGEN 4.x