jenkinsci / jenkinsci/workflow-basic-steps-plugin
[JENKINS-62053] Retry does not abort if a failure has happened during parallel executions
- Dominant language
- Java
- Stars
- 73
- Forks
- 129
- PR merge metrics
- No merged PRs in 30d
Description
When wrapping parallel steps in a retry block, if you attempt to abort the run after a stage has failed, it will continue retrying instead of aborting. Jenkins will also mark the build result as aborted, even though it continued with the retry and failed. Because of this the stop button in Blue Ocean will be grayed out, until the page is refreshed. And the only way to get the pipeline to finally abort, is to either abort it before a failure happens, or manually abort each retry.
node {
stage('one') {
sleep 5
}
stage('two') {
retry(3) {
parallel slowTask1: {
sleep 30
}, slowTask2: {
sleep 30
}, failingTask: {
sh 'exit 1'
},
failFast: false
}
}
}
---
Originally reported by wafflestomp, imported from: Retry does not abort if a failure has happened during parallel executions
Raw content of original issue
When wrapping parallel steps in a retry block, if you attempt to abort the run after a stage has failed, it will continue retrying instead of aborting. Jenkins will also mark the build result as aborted, even though it continued with the retry and failed. Because of this the stop button in Blue Ocean will be grayed out, until the page is refreshed. And the only way to get the pipeline to finally abort, is to either abort it before a failure happens, or manually abort each retry.
node {
stage('one') {
sleep 5
}
stage('two') {
retry(3) {
parallel slowTask1: {
sleep 30
}, slowTask2: {
sleep 30
}, failingTask: {
sh 'exit 1'
},
failFast: false
}
}
}
environment
```
Jenkins = 2.204.2
Pipeline: Basic Steps = 2.19
```
2 attachments
- [Screen Shot 2020-04-25 at 10.37.32 AM.png](https://issues.jenkins.io/secure/attachment/51071/Screen%20Shot%202020-04-25%20at%2010.37.32%20AM.png)
> 
- [Screen Shot 2020-04-25 at 10.38.12 AM.png](https://issues.jenkins.io/secure/attachment/51072/Screen%20Shot%202020-04-25%20at%2010.38.12%20AM.png)
> 
Contributor guide
Assessment
This issue has not been assessed yet.