Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
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
- is blocked by
-
JENKINS-35989 Allow for Restartable Pipeline Step
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- links to
Activity
| 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. |
| Component/s | workflow-plugin [ 18820 ] | |
| Component/s | pipeline-stage-view-plugin [ 21139 ] |
| Assignee | Antonio Muñiz [ amuniz ] |
| Resolution | Won't Do [ 10001 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Jean-Marc Collin
made changes -
| Link |
This issue is duplicated by |
| Workflow | JNJira [ 169841 ] | JNJira + In-Review [ 198709 ] |
| Component/s | pipeline-general [ 21692 ] |
| Component/s | workflow-plugin [ 18820 ] |
dan tran
made changes -
| Link |
This issue is blocked by |
Sadiq Khoja
made changes -
| Resolution | Won't Do [ 10001 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Component/s | pipeline-model-definition-plugin [ 21706 ] | |
| Component/s | pipeline [ 21692 ] |
| Status | Reopened [ 4 ] | Open [ 1 ] |
| Assignee | CloudBees Inc. [ cloudbees ] |
| Component/s | pipeline [ 21692 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
Sumit Kumar
made changes -
| Assignee | CloudBees Inc. [ cloudbees ] | Sumit Kumar [ jenkins_pipeline_blue ] |
Sumit Kumar
made changes -
| Assignee | Sumit Kumar [ jenkins_pipeline_blue ] | CloudBees Inc. [ cloudbees ] |
| Component/s | pipeline-model-definition-plugin [ 21706 ] |
| Link |
This issue relates to |
| 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. |
| 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 ( 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. |
| 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 ( 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 ( 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. |
| Status | In Progress [ 3 ] | Open [ 1 ] |
| 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 ( 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 ( 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. |
| 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 ( 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 ( 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. |
| Assignee | CloudBees Inc. [ cloudbees ] |
| 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 ( 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 ( 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. |
| Remote Link | This issue links to "CloudBees Internal CD-244 (Web Link)" [ 19093 ] |
| Rank | Ranked lower |