Actions
Feature #4508
open
[Documentation] Best practices for getting the most out of job re-use
Status:
New
Priority:
Normal
Assigned To:
-
Category:
Documentation
Target version:
-
Start date:
11/12/2014
Due date:
% Done:
0%
Estimated time:
Story points:
1.0
Description
Not sure how to name this, but I ran into the situation where:
I have 10 jobs running in a pipeline, and 9 complete and 1 fail. Each job calls a unique script in my git repo. I've set the script_version to master on each job so that I wouldn't have to change the script version every time I make a commit. I edit that one script where the job fails and make a commit/push. I then use re-run with latest so arvados would account for my new repo. All 10 jobs re-run, which is not intended because I only wanted the one that failed to re-run to run.
It would be nice to have the pipeline-runner to be able to see if the scripts that have successfully completed a job have changed before re-running the job.
Updated by 
Updated by
Actions