[JIRA] (JENKINS-14656) Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually

[ch...@masto.com (JIRA)]

Christopher Masto commented on JENKINS-14656 Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually I've been struggling with the same problem for the past couple of days. It seems like both plugins are slightly broken; the Build Pipeline doesn't set up the environment exactly the same for its manually-triggered jobs as an auto-triggered downstream build does: for example, the log doesn't always say Started by upstream project "test_upstream" build number 30 (although sometimes it does, and I haven't figured out the difference). Setting a Run Parameter works consistently but only in one of the two pipelines I created. I think Build Pipelines is a bit buggy but I don't understand enough about the internals to make sense of the symptoms. Looking at build.xml from a manually triggered vs automatically triggered build, the manual one seems to have an amalgam of system configuration, the upstream project's configuration, and the downstream one. It looks wrong to me. Regardless, since the downstream job does always have upstream build information available, Copy Artifact ought to be able to use it. It would be nice to have the option to use a standard Run Parameter rather than the special copy parameter that other plugins don't know how to set.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira