[JIRA] [build-pipeline-plugin] (JENKINS-32885) Build Pipeline Plugin doesn't link the jobs to it's corresponding build number after successful re-build.

[niraj.kha...@live.com (JIRA)]

Title: Message Title

Niraj Khanal updated an issue   Jenkins / JENKINS-32885 Build Pipeline Plugin doesn't link the jobs to it's corresponding build number after successful re-build. This is a blocker issue for us at the moment because the specific build designated to go to production cannot move further down the pipeline when this build ( succeeds on retry) but fails to display it in the build-pipeline view. So even though the build is successful, the pipeline shows red and the next job in the pipeline doesn't have a trigger. If we try to run the build from the list, it loses all of it's parameters so we can't go that way either. The only way right now is to re-run the pipeline which will create another artifact with a different version and has to go through each environment once again which adds another complexity because now the build asset has a different version ( which is tied to the build number). Any suggestions or workaround until it's fixed is welcome. Thanks Change By: Niraj Khanal Priority: Major Blocker 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.