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

Restart pipeline from specific stage, after failure

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: pipeline
    • Labels:
      None
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            michaelhuettermann Michael Hüttermann created issue -
            michaelhuettermann Michael Hüttermann made changes -
            Field Original Value New Value
            Description 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.
            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.
            amuniz Antonio Muñiz made changes -
            Component/s workflow-plugin [ 18820 ]
            Component/s pipeline-stage-view-plugin [ 21139 ]
            amuniz Antonio Muñiz made changes -
            Assignee Antonio Muñiz [ amuniz ]
            jglick Jesse Glick made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Won't Do [ 10001 ]
            jmcollin Jean-Marc Collin made changes -
            Link This issue is duplicated by JENKINS-36813 [ JENKINS-36813 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 169841 ] JNJira + In-Review [ 198709 ]
            abayer Andrew Bayer made changes -
            Component/s pipeline-general [ 21692 ]
            abayer Andrew Bayer made changes -
            Component/s workflow-plugin [ 18820 ]
            dantran dan tran made changes -
            Link This issue is blocked by JENKINS-35989 [ JENKINS-35989 ]
            sadiqkhoja Sadiq Khoja made changes -
            Resolution Won't Do [ 10001 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            jglick Jesse Glick made changes -
            Component/s pipeline-model-definition-plugin [ 21706 ]
            Component/s pipeline [ 21692 ]
            jglick Jesse Glick made changes -
            Status Reopened [ 4 ] Open [ 1 ]
            hrmpw Patrick Wolf made changes -
            Assignee CloudBees Inc. [ cloudbees ]
            hrmpw Patrick Wolf made changes -
            Component/s pipeline [ 21692 ]
            hrmpw Patrick Wolf made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jenkins_pipeline_blue Sumit Kumar made changes -
            Assignee CloudBees Inc. [ cloudbees ] Sumit Kumar [ jenkins_pipeline_blue ]
            jenkins_pipeline_blue Sumit Kumar made changes -
            Assignee Sumit Kumar [ jenkins_pipeline_blue ] CloudBees Inc. [ cloudbees ]
            abayer Andrew Bayer made changes -
            Component/s pipeline-model-definition-plugin [ 21706 ]
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-45455 [ JENKINS-45455 ]
            jamesdumay James Dumay made changes -
            Description 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.
            {panel:title=Improvement on roadmap|titleBGColor=#3878de|titleColor=white}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates.
            {panel}


            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.
            jamesdumay James Dumay made changes -
            Description {panel:title=Improvement on roadmap|titleBGColor=#3878de|titleColor=white}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates.
            {panel}


            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.
            {panel:title=This feature is unplanned and not actively being worked on|titleBGColor=grey|titleColor=white}
            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.

            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|https://jenkins.io/projects/blueocean/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. If you have any questions, please don't hesitate to comment.
            {panel}


            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.
            jamesdumay James Dumay made changes -
            Description {panel:title=This feature is unplanned and not actively being worked on|titleBGColor=grey|titleColor=white}
            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.

            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|https://jenkins.io/projects/blueocean/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. If you have any questions, please don't hesitate to comment.
            {panel}


            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.
            {panel:title=This feature is unplanned and not actively being worked on|titleBGColor=grey|titleColor=white}

            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|https://jenkins.io/projects/blueocean/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. If you have any questions, please don't hesitate to comment.

            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.
            {panel}


            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.
            jamesdumay James Dumay made changes -
            Status In Progress [ 3 ] Open [ 1 ]
            jamesdumay James Dumay made changes -
            Description {panel:title=This feature is unplanned and not actively being worked on|titleBGColor=grey|titleColor=white}

            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|https://jenkins.io/projects/blueocean/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. If you have any questions, please don't hesitate to comment.

            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.
            {panel}


            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.
            {panel:title=This feature is unplanned and not actively being worked on|titleBGColor=grey|titleColor=white}

            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|https://jenkins.io/projects/blueocean/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.
            {panel}


            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.
            jamesdumay James Dumay made changes -
            Description {panel:title=This feature is unplanned and not actively being worked on|titleBGColor=grey|titleColor=white}

            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|https://jenkins.io/projects/blueocean/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.
            {panel}


            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.
            {panel:title=This feature is unplanned and not actively being worked on|titleBGColor=grey|titleColor=white}

            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|https://jenkins.io/projects/blueocean/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
            {panel}


            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.
            jamesdumay James Dumay made changes -
            Assignee CloudBees Inc. [ cloudbees ]
            jamesdumay James Dumay made changes -
            Description {panel:title=This feature is unplanned and not actively being worked on|titleBGColor=grey|titleColor=white}

            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|https://jenkins.io/projects/blueocean/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
            {panel}


            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.
            {panel:title=This feature is unplanned and not actively worked on|titleBGColor=grey|titleColor=white}

            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|https://jenkins.io/projects/blueocean/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
            {panel}


            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.
            cloudbees CloudBees Inc. made changes -
            Remote Link This issue links to "CloudBees Internal CD-244 (Web Link)" [ 19093 ]
            shanexpert28 shan shan made changes -
            Rank Ranked lower

              People

              • Assignee:
                Unassigned
                Reporter:
                michaelhuettermann Michael Hüttermann
              • Votes:
                146 Vote for this issue
                Watchers:
                187 Start watching this issue

                Dates

                • Created:
                  Updated: