[JIRA] (JENKINS-62053) Retry does not abort if a failure has happened during parallel executions

[email protected] (JIRA) Sat, 25 Apr 2020 07:45:39 -0700

Title: Message Title

John Pastore created an issue

JENKINS-62053

Issue Type:	Bug
Assignee:	Unassigned
Attachments:	Screen Shot 2020-04-25 at 10.37.32 AM.png, Screen Shot 2020-04-25 at 10.38.12 AM.png
Components:	workflow-basic-steps-plugin
Created:	2020-04-25 14:44
Environment:	Jenkins = 2.204.2 Pipeline: Basic Steps = 2.19
Labels:	plugin
Priority:	Minor
Reporter:	John Pastore

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
        }
    }
}
 
                                                            

Add Comment

This message was sent by Atlassian Jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205950.1587825867000.17730.1587825900091%40Atlassian.JIRA.

[JIRA] (JENKINS-62053) Retry does not abort if a failure has happened during parallel executions

Reply via email to