Arvados

5653-arv-copy-multiple-branches-wip is up for review. I tested it by copying the same pipeline template in this bug report to my Docker installation, and it correctly copied over both branches. Here's a transcript for illustration (it doesn't copy over any collections because that was already done in a previous run):

brinstar % arv-copy --src tb05z --dst bcsdk --dst-git-repo=brett/copy5653b --project-uuid=bcsdk-j7d0g-bwfjcexaeflb36m tb05z-p5p6p-wp8680agywvi2fo
WARNING: 'sguthrie' is an alias for 'tb05z-s0uqq-y6tb5g8u0fzdizd'
remote: Counting objects: 158, done.
remote: Compressing objects: 100% (78/78), done.
remote: Total 158 (delta 34), reused 0 (delta 0)
Receiving objects: 100% (158/158), 16.18 KiB, done.
Resolving deltas: 100% (34/34), done.
WARNING: 'brett/copy5653b' is an alias for 'bcsdk-s0uqq-3mcn7ujkrec3997'
Counting objects: 82, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (24/24), done.
Writing objects: 100% (82/82), 8.57 KiB, done.
Total 82 (delta 16), reused 81 (delta 16)
To git@api.dev.arvados:brett/copy5653b.git
 * [new branch]      git_git_tb05z_arvadosapi_com_sguthrie_git_filter_vcfs -> git_git_tb05z_arvadosapi_com_sguthrie_git_filter_vcfs
WARNING: 'brett/copy5653b' is an alias for 'bcsdk-s0uqq-3mcn7ujkrec3997'
Counting objects: 71, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (18/18), done.
Writing objects: 100% (68/68), 6.97 KiB, done.
Total 68 (delta 16), reused 68 (delta 16)
To git@api.dev.arvados:brett/copy5653b.git
 * [new branch]      git_git_tb05z_arvadosapi_com_sguthrie_git_run_cava -> git_git_tb05z_arvadosapi_com_sguthrie_git_run_cava
2015-04-06 14:39:08 arvados.arv-copy[478] INFO:
2015-04-06 14:39:08 arvados.arv-copy[478] INFO: Success: created copy with uuid bcsdk-p5p6p-v1f4wqe910dqxei

This probably qualifies as bikeshedding, but would this be a good opportunity to take advantage of the new capability to create repositories, instead of the current practice of cramming branches into unrelated repositories?

Peter Amstutz wrote:

This probably qualifies as bikeshedding, but would this be a good opportunity to take advantage of the new capability to create repositories, instead of the current practice of cramming branches into unrelated repositories?

It's not exactly bikeshedding (the same idea crossed my mind) but as part of my support work I think addressing some of the other bugs in triage is higher priority than this. Users have an easy workaround of making the repository themselves, then feeding it to arv-copy if they want. Thanks for filing #5676.

9b0ace3 LGTM.

Repository creating feature request filed separately at #5676.