[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven

[jayme...@gmail.com (JIRA)]

Jay Meyer created JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 01/Oct/12 2:50 PM Description: Given: Jenkins has different build jobs with different versions of the same artifacts and group ids. Example jarProj-1.1 and jarProj-1.2, and dependent builds warProj-1.1 and warProj-1.2. Problem: When Jenkins determines downstream build jobs, it is choosing ALL versions of old and current jobs. So in the example, jarProj-1.2 kicks off BOTH warProj-1.2 (correct) AND warProj1.1 (incorrect). Also, jarProj-1.1 kicks off no builds at all (incorrect), when instead we expect it to kick off warProj-1.1. Seems related to JENKINS-15295. We have the same fingerprint errors. Also, JENKINS-12735 made a change to cover version ranges in Maven, and that seems like it would break the downstream builds if a bug was introduced there. Project: Jenkins Priority: Critical Reporter: Jay Meyer

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