Actions
Idea #3196
closedImprove "clone pipeline" / "re-run pipeline" feature
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
Story points:
-
Description
The current "Clone and edit" button on the pipeline instance view has several bugs and limitations:
- If component job B depends on A, and component job A ran successfully, the "output_of" dependency input of B is replaced with the output of job A. However, if job A' runs and produces a different output, job B' will use the original output from A and not A'.
- User cannot specify whether the jobs should use the exact same script version hash or re-resolve the script version. Currently it always re-resolves the script version provided in the components, so the user cannot specifically ask for the exact same run. This problem exists for docker image tags.
- User cannot specify whether or not successful component jobs should be re-used in the new instance (based on both the automatic job re-use logic, or re-using successful component jobs outside of the re-use logic).
- If the user has updated the original template, they cannot tell it to use the new template with the same inputs. Depends on story #3090
Actions