[JIRA] (JENKINS-15237) Dependent Maven Jobs ignore version-number

Mathias Blasek created JENKINS-15237

Dependent Maven Jobs ignore version-number

Issue Type:	Bug
Assignee:	Unassigned
Components:	core, maven
Created:	19/Sep/12 7:19 PM
Description:	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?
Environment:	Windows Jenkins ver. 1.481 Maven 3.0.3
Project:	Jenkins
Labels:	jenkins maven
Priority:	Minor
Reporter:	Mathias Blasek

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

Jan Zuchhold commented on JENKINS-15237

Dependent Maven Jobs ignore version-number

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

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

 

Jan Zuchhold edited a comment on JENKINS-15237

Dependent Maven Jobs ignore version-number

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

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

Marco Rothe commented on JENKINS-15237

Dependent Maven Jobs ignore version-number

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!

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

Marco Rothe updated JENKINS-15237

Dependent Maven Jobs ignore version-number

Changed priority to major because this bug cause a heavy load to build infrastructure.
Change By:	Marco Rothe (28/Sep/12 9:40 AM)
Priority:	Minor Major

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

Julien Carsique commented on JENKINS-15237

Dependent Maven Jobs ignore version-number

Given the number of jobs we have, the issue is critical/blocker for us. See http://qa.nuxeo.org/jenkins/job/nuxeo-core-master/ 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.

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

 

Julien Carsique edited a comment on JENKINS-15237

Dependent Maven Jobs ignore version-number

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.

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

Julien Carsique commented on JENKINS-15237

Dependent Maven Jobs ignore version-number

Complementary info: not specific to Windows, nor Maven 3; reproduced on Linux, Maven 2.2.1, Jenkins 1.481 to 1.491

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

 

Julien Carsique edited a comment on JENKINS-15237

Dependent Maven Jobs ignore version-number

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

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

Andrei Pozolotin commented on JENKINS-15237

Dependent Maven Jobs ignore version-number

I am curious is this really fixed by #15367 ?

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

 

Andrei Pozolotin edited a comment on JENKINS-15237

Dependent Maven Jobs ignore version-number

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

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

 

Andrei Pozolotin edited a comment on JENKINS-15237

Dependent Maven Jobs ignore version-number

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

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