Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33846

Restart pipeline from specific stage, after failure

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • pipeline
    • None

      This feature is unplanned and not actively worked on

      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.

          [JENKINS-33846] Restart pipeline from specific stage, after failure

          Michael Hüttermann created issue -
          Michael Hüttermann made changes -
          Description Original: 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.           		New: 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.
          Antonio Muñiz made changes -
          Component/s New: workflow-plugin [ 18820 ]
          Component/s Original: pipeline-stage-view-plugin [ 21139 ]
          Antonio Muñiz made changes -
          Assignee Original: Antonio Muñiz [ amuniz ]

          Antonio Muñiz added a comment -

          This feature is available in a proprietary plugin by CloudBees, this is the documentation.

          Antonio Muñiz added a comment - This feature is available in a proprietary plugin by CloudBees, this is the documentation .

          Michael Hüttermann added a comment -

          Hi amuniz,
          thanks for the hint. I think introducing a "checkpoint" is not necessary, since every single Stage should operate as a checkpoint.
          I'd like to see this in the free Jenkins distribution.

          Michael Hüttermann added a comment - Hi amuniz , thanks for the hint. I think introducing a "checkpoint" is not necessary, since every single Stage should operate as a checkpoint. I'd like to see this in the free Jenkins distribution.

          Jesse Glick added a comment -

          No current plans to release this feature as OSS.

          Jesse Glick added a comment - No current plans to release this feature as OSS.
          Jesse Glick made changes -
          Resolution New: Won't Do [ 10001 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Jean-Marc Collin added a comment -

          Such a shame... Without this feature, Workflow will NEVER replace "Deployment Pipeline" plugin in a PRODuction environment.
          Pipeline can be wide and slow and restarting a Pipeline entirely at each failure is simply not imaginable in the real life (but only in demos).

          I really don't understand that Cloudbees could be an obstacle to the adoption of Workflow. It never have such a position (for what I'm knowing) in the past.

          Can you please consider re-opening this fundamental issue ?

          Jean-Marc

          Jean-Marc Collin added a comment - Such a shame... Without this feature, Workflow will NEVER replace "Deployment Pipeline" plugin in a PRODuction environment. Pipeline can be wide and slow and restarting a Pipeline entirely at each failure is simply not imaginable in the real life (but only in demos). I really don't understand that Cloudbees could be an obstacle to the adoption of Workflow. It never have such a position (for what I'm knowing) in the past. Can you please consider re-opening this fundamental issue ? Jean-Marc
          Jean-Marc Collin made changes -
          Link New: This issue is duplicated by JENKINS-36813 [ JENKINS-36813 ]

            Unassigned Unassigned
            michaelhuettermann Michael Hüttermann
            Votes:
            156 Vote for this issue
            Watchers:
            194 Start watching this issue

              Created:
              Updated: