[JIRA] [promoted-builds] (JENKINS-16213) the downstream build result was not updated correctly when it is triggered by multiple builds
Jesse Glick commented on JENKINS-16213 the downstream build result was not updated correctly when it is triggered by multiple builds I am doubtful that introducing a new option is necessary here. Probably a user error (failure to properly associate upstream and downstream builds via fingerprints); if fingerprints are in use and it is still promoting the wrong build, that is simply a bug that should not require the user to configure anything differently. 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/d/optout.
[JIRA] [promoted-builds] (JENKINS-16213) the downstream build result was not updated correctly when it is triggered by multiple builds
Kari Sivonen assigned JENKINS-16213 to Kari Sivonen the downstream build result was not updated correctly when it is triggered by multiple builds Change By: Kari Sivonen (25/Sep/14 11:37 AM) Assignee: liwei KariSivonen 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/d/optout.
[JIRA] [promoted-builds] (JENKINS-16213) the downstream build result was not updated correctly when it is triggered by multiple builds
Kari Sivonen commented on JENKINS-16213 the downstream build result was not updated correctly when it is triggered by multiple builds To do this more cleaver, I take example from copy artifact plugin where is introduced global and job's parameter upstreamFilterStrategy. In Global parameter there is options UseOldest and UseNewest. In job configuration there is als option UseGlobalSetting. Depending selection latest or oldest job is promoted. 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/d/optout.
