Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-15367

Jenkins kicks off the wrong downstream builds for Maven

      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.

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

          Jay Meyer created issue -
          Jay Meyer made changes -
          Component/s New: maven-dependency-update-trigger [ 15756 ]
          Component/s New: maven2 [ 15487 ]
          Jay Meyer made changes -
          Link New: This issue is related to JENKINS-12735 [ JENKINS-12735 ]

          Larry Shatzer, Jr. added a comment - See this thread https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/sPD02rg0ZCQ
          Kohsuke Kawaguchi made changes -
          Assignee New: Kohsuke Kawaguchi [ kohsuke ]

          Marco Rothe added a comment - - edited

          It seems to be related to (or a dublicate of) 15237.

          This is a real blocker for us and we downgraded to 1.480.

          Marco Rothe added a comment - - edited It seems to be related to (or a dublicate of) 15237. This is a real blocker for us and we downgraded to 1.480.
          Marco Rothe made changes -
          Link New: This issue is related to JENKINS-15237 [ JENKINS-15237 ]

          Alex Koon added a comment -

          I have traced this issue as part of

          https://issues.jenkins-ci.org/browse/JENKINS-12735

          I have added a test case to MavenModuleTest to show this and a fix for this in ModuleDependency. I have pushed this to my fork on github at

          https://github.com/alexkoon/jenkins

          and the commit is at

          https://github.com/alexkoon/jenkins/commit/4043905580df5bf22cde0eaf3dec103abdc88017

          I can issue a pull request for this if you wish.

          Alex Koon added a comment - I have traced this issue as part of https://issues.jenkins-ci.org/browse/JENKINS-12735 I have added a test case to MavenModuleTest to show this and a fix for this in ModuleDependency. I have pushed this to my fork on github at https://github.com/alexkoon/jenkins and the commit is at https://github.com/alexkoon/jenkins/commit/4043905580df5bf22cde0eaf3dec103abdc88017 I can issue a pull request for this if you wish.

          Hi,
          I did try out your fork, and it seems to work fine for my scenarios. (i.e. direct snapshot dependencies got triggered, other versions didn't)

          Michael Glauche added a comment - Hi, I did try out your fork, and it seems to work fine for my scenarios. (i.e. direct snapshot dependencies got triggered, other versions didn't)

          Erik Riemers added a comment -

          Would be nice to see this in 1.491 or newer.

          Erik Riemers added a comment - Would be nice to see this in 1.491 or newer.

            olamy Olivier Lamy
            jaymeyer Jay Meyer
            Votes:
            35 Vote for this issue
            Watchers:
            42 Start watching this issue

              Created:
              Updated:
              Resolved: