-
New Feature
-
Resolution: Unresolved
-
Major
-
None
The use case for restarting stages of a Pipeline is an important one and as such we intend to include this feature in Declarative Pipeline (JENKINS-45455) as open source. I have put this feature on the Declarative Pipeline roadmap. I encourage you to review JENKINS-45455 and leave a comment to ensure that your use case is covered.
For the purpose of clarity, we will not be providing this feature for scripted pipelines.
After review of the Checkpoints feature, the CloudBees team have come to the decision that will not be open sourcing Checkpoints. I know we had signalled in this issue that we would be open sourcing this feature and I am sincerely sorry to disappoint those who have been waiting for us to do so.
Thanks,
James Dumay
Product Manager, CloudBees Inc
It would be fine, and customers ask me for that continuously to have the function to again start a failed pipeline,but not at the very beginning, rather at a stage along the pipeline chain, particularly a stage which failed before during a former run,and the cause of the failure was fixed.
Maybe I've chosen the wrong "component" for this ticket. Please feel free to adjust accordingly.
Tested on Jenkins ver. 2.0-beta-1, and its new Pi Pipeline item.
- is blocked by
-
JENKINS-35989 Allow for Restartable Pipeline Step
-
- Closed
-
- is duplicated by
-
JENKINS-36813 Re-run particular steps or stage
-
- Closed
-
- relates to
-
JENKINS-45455 Restarting stages
-
- Closed
-
- links to
jamesdumay - so ...
... I'm rather unsure how to interpret this: checkpoint is already implemented, so any reference to "less complexity" is either handwaving, or the checkpoint feature you currently want to us to pay for^[a]^ doesn't work properly.
I'll note, as others, that the inability to have checkpoints in jenkins pipeline makes it pretty much useless to us. (workarounds like https://stackoverflow.com/a/40351693/321013 and other mentioned ones non-withstanding)
([a]: I'm fine with you trying to make a buck. It's just that I feel the checkpoint feature is not enterprisey at all - it seems vital for any non-trivial long-running pipeline, also (and maybe especially) for small teams.)