|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-12735) No upstream or downstre... jayme...@gmail.com (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... jayme...@gmail.com (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... mich...@glauche.de (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... mich...@glauche.de (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... alexk...@hotmail.com (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... jayme...@gmail.com (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... jayme...@gmail.com (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... mich...@glauche.de (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... mich...@glauche.de (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... aherit...@apache.org (JIRA)
- [JIRA] (JENKINS-12735) No upstream or dow... alexk...@hotmail.com (JIRA)
in Jenkins 1.482, this is causing Jenkins to kick off downstream builds of un-related versions.
Example: mygrp-projCore-3.4 is kicking off mygrp-projWeb-3.4 (which is correct) and also the old mygrp-projWeb-3.3. The old projWeb artifact id matches, but the version does not match. So when Jenkinds is configured to build both versions in different jobs, Jenkins is kicking off all versions of old downstream jobs.