Bug #9049
Updated by Brett Smith about 8 years ago
A user writes a pipeline template following our "Git strategy for pipeline development":https://dev.arvados.org/projects/arvados/wiki/Git_strategy_for_pipeline_development. They set filters to determine what jobs are eligible for reuse, including a repository filter.
Another user uses @arv copy@ to copy this template somewhere else. The destination Git repository has a different name. However, @arv copy@ does not adjust the filters.
At this point, the pipeline template won't run as intended on the destination cluster. Best case, there is no Git repository on the destination cluster with the same name as the source repository, so the run fails almost immediately. Worst case, there _is_ a Git repository with the same name on the destination cluster, and then something unpredictable happens.