Feature #11515

[CWL] [Workbench] Support for copying/moving pipelines

Added by Jiayong Li over 4 years ago. Updated 3 months ago.

Assigned To:
Target version:
Start date:
Due date:
% Done:


Estimated time:
Story points:


A common practice for writing a pipeline is to first test it in a private project, e.g. Home, because we don't want to clutter the production project since tests tend to be error-prone. Ultimately the successful pipeline run needs to be in the production project that's shared with customers, but as of now, there's no way of copying/moving the jobs and output collections of the successful test pipeline.

We need a feature integrated in Workbench to copy/move pipelines.


#1 Updated by Jiayong Li over 4 years ago

  • Description updated (diff)

#2 Updated by Bryan Cosca over 4 years ago

A workaround would be to do:

arv-copy --src cluster_uuid --dst cluster_uuid --dst-git-repo any_repo pipeline_uuid to move the pipeline instance and top level jobs.

Then clone https://github.com/bcosc/arvados-tools/blob/master/copy-cwl-pi.py and run

python copy-cwl-pi.py pi_uuid project_uuid

to move all the outputs and log collections of all the child jobs.

I'm unsure what else would need to be copied, but that can be added to copy-cwl-pi.py

#3 Updated by Tom Morris about 4 years ago

  • Target version set to Arvados Future Sprints

#4 Updated by Peter Amstutz 3 months ago

  • Target version deleted (Arvados Future Sprints)

Also available in: Atom PDF