[JIRA] [build-flow-plugin] (JENKINS-30942) retry still trying after build has been aborted
Title: Message Title Damien Nozay assigned an issue to Unassigned Jenkins / JENKINS-30942 retry still trying after build has been aborted Change By: Damien Nozay Assignee: Damien Nozay Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-30942) retry still trying after build has been aborted
Title: Message Title Baptiste Mathus assigned an issue to Damien Nozay Jenkins / JENKINS-30942 retry still trying after build has been aborted Change By: Baptiste Mathus Assignee: Nicolas De Loof Damien Nozay Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-30942) retry still trying after build has been aborted
Title: Message Title
Bertrand Roussel created an issue
Jenkins / JENKINS-30942
retry still trying after build has been aborted
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
build-flow-plugin
Created:
14/Oct/15 9:26 AM
Environment:
Jenkins ver. 1.609.3 build-flow-plugin 0.18
Priority:
Major
Reporter:
Bertrand Roussel
Given a structure like this:
parallel ( // job 1, 2 and 3 will be scheduled in parallel. { retry(3) { build("job1") }
}, { retry(2) { build("job2") }
} )
If I abord manally the main build, current builds for job1 and job2 will abort, but retry will ... retry to builds these jobs even though everything is aborted.
There is a 'worstAllowed' parameter, but given that ABORT is the 'worst' Result, I don't think I can catch it without accepting all other failures.
It feels like upon failure, retry should check the state of the current build before rescheduling a new build.
