[JIRA] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin

[jeanf...@arachnys.com (JIRA)]

Title: Message Title

Jean-Frédéric commented on JENKINS-29652   Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin I encounter the same issue as Chris with my build pipeline − multiplied: jobA triggers 3 parallel builds that join in jobE, which builds an artifact and triggers in 6 parallel testing jobs, which join in one deployjob jobL which triggers 6 other testing jobs which join in a switchover job. When something goes wrong in one of the join, we can restart jobA, jobE or jobL, but that is a waste. Regarding the ambiguity question: I do realise it is an issue. I would have thought though that jobs know which particular build they triggered. jobA#1 → jobB#1 ✖ jobA#2 → jobB#2 ✖ Restart jobB#3 → jobC here, jobA#1 does not get notified that jobB#3 succeeded as it is not its upstream parent. Or am I missing something ? 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.