|
||||||||
|
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 |
||||||||
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/groups/opt_out.
In an older Jenkins version (1.486, with build-pipeline 1.3.3) I looked up the /api/json for two deploy builds of the downstream project and noticed that the parameters are the same despite being triggered by different upstream builds in two separate pipelines. I also noticed the build-pipeline plugin modified the <publishers/> tag of the downstream project during the first deploy build, but with the second the publisher tag is left unmodified.
In effect, the downstream project deployed the same application twice.