-
Bug
-
Resolution: Fixed
-
Critical
-
None
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.
- is related to
-
JENKINS-12735 No upstream or downstream resolution with Maven version ranges
-
- Resolved
-
-
JENKINS-15237 Dependent Maven Jobs ignore version-number
-
- Resolved
-
[JENKINS-15367] Jenkins kicks off the wrong downstream builds for Maven
Component/s | New: maven-dependency-update-trigger [ 15756 ] | |
Component/s | New: maven2 [ 15487 ] |
Link |
New:
This issue is related to |
Assignee | New: Kohsuke Kawaguchi [ kohsuke ] |
Link |
New:
This issue is related to |
See this thread https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/sPD02rg0ZCQ