• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core, maven-plugin
    • Windows
      Jenkins ver. 1.481
      Maven 3.0.3

      After updating my jenkins server to version 1.481, the maven dependencies (version-number) will not be resolved correctly anymore. Let me give you an example to explain the problem in detail:

      I have two projects "BASE" and "DELTA". Both projects are hosted on a svn-repository. Project DELTA exists only in trunk, project BASE in trunk (ver. 0.2.0-SNAPSHOT) and in a branch (ver. 0.1.3-SNAPSHOT). The DELTA-branch has a dependency on an stable BASE-version (ver. 0.2.2, which can be found on a nexus repository), DELTA-trunk depends on BASE-SNAPSHOT version. On Jenkins I created three "maven2/3 projects" (BASE, DELTA and DELTA-branch). I set up the configuration for every project in the same way: checked the options "Build whenever a SNAPSHOT dependency is built", "Poll SCM" on "Build Triggers" and checked "Resolve Dependencies during Pom parsing" in the "Build"-section.
      When I commit sources of the BASE-Project, Jenkins will built the BASE-job. After finishing, he will start both DELTA-jobs without checking the version-number of the dependency. I would expect that Jenkins would only built the DELTA-trunk project like the older version of Jenkins (ver.1.438). Can you tell me anything that has changed with the new version that my caused this problem or give me a solution for my problem?

          [JENKINS-15237] Dependent Maven Jobs ignore version-number

          Jan Zuchhold added a comment - - edited

          I can confirm this problem, downgrading to 1.480 is a workaround.

          $10 reward for a fix of this: http://www.freedomsponsors.org/core/issue/29/dependent-maven-jobs-ignore-version-number

          Jan Zuchhold added a comment - - edited I can confirm this problem, downgrading to 1.480 is a workaround. $10 reward for a fix of this: http://www.freedomsponsors.org/core/issue/29/dependent-maven-jobs-ignore-version-number

          Marco Rothe added a comment -

          I can confirm the problem too (jenkins 1.483)

          It seems that not only the SNAPSHOT version is ignored. I see a project (which depends on a release version dependency!) build triggert by a upstream build of the completely unrelated SNAPSHOT version of that dependency. Therefore our complete jenkins build server kept busy by building unrelated projects. Very annoying!

          Marco Rothe added a comment - I can confirm the problem too (jenkins 1.483) It seems that not only the SNAPSHOT version is ignored. I see a project (which depends on a release version dependency!) build triggert by a upstream build of the completely unrelated SNAPSHOT version of that dependency. Therefore our complete jenkins build server kept busy by building unrelated projects. Very annoying!

          Marco Rothe added a comment -

          Changed priority to major because this bug cause a heavy load to build infrastructure.

          Marco Rothe added a comment - Changed priority to major because this bug cause a heavy load to build infrastructure.

          Julien Carsique added a comment - - edited

          Given the number of jobs we have, the issue is critical/blocker for us. See http://qa.nuxeo.org/jenkins/job/nuxeo-core-master/462

          The strange thing is the dependency between projects which is reported when clicking on a fingerprint is right:

          But, given the above sample, nuxeo-services-5.6.0 which has no dependency relation with nuxeo-core-master is badly triggered anyway.

          Julien Carsique added a comment - - edited Given the number of jobs we have, the issue is critical/blocker for us. See http://qa.nuxeo.org/jenkins/job/nuxeo-core-master/462 The strange thing is the dependency between projects which is reported when clicking on a fingerprint is right: effective relationship: http://qa.nuxeo.org/jenkins/projectRelationship?lhs=nuxeo-core-master&rhs=nuxeo-services-master no relationship: http://qa.nuxeo.org/jenkins/projectRelationship?lhs=nuxeo-core-master&rhs=nuxeo-services-5.6.0 But, given the above sample, nuxeo-services-5.6.0 which has no dependency relation with nuxeo-core-master is badly triggered anyway.

          Julien Carsique added a comment - - edited

          Great to see it fixed in JENKINS-15367, for 1.492

          Julien Carsique added a comment - - edited Great to see it fixed in JENKINS-15367 , for 1.492

          Andrei Pozolotin added a comment - - edited

          I am curious is this really fixed by #JENKINS-15367 ?

          Andrei Pozolotin added a comment - - edited I am curious is this really fixed by # JENKINS-15367 ?

          evernat added a comment -

          This issue seems to have been fixed by JENKINS-15367 in Jenkins v1.492.
          Please reopen if not.

          evernat added a comment - This issue seems to have been fixed by JENKINS-15367 in Jenkins v1.492. Please reopen if not.

            Unassigned Unassigned
            sib_hobbit Mathias Blasek
            Votes:
            35 Vote for this issue
            Watchers:
            33 Start watching this issue

              Created:
              Updated:
              Resolved: