![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Attachments:
|
jscheel_config.xml |
|
Components:
|
core, maven-plugin |
|
Created:
|
18/Mar/15 2:26 AM
|
|
Description:
|
When our developerss push a new snapshot version to our subversion repository for Project A, it will trigger all the module jobs for Project A (ProjectA-core, ProjectA-base, ProjectA-parent, etc) via SCM. During this initial SCM triggered run, builds will run out of order. My initial thought is that this is because builds are now referencing new snapshots in the pom.xml, so the dependencies based on old versions of the pom.xml are no longer used. This makes sense on a build by build basis, but having this happen to many interconnected modules means dependencies are only being added for modules that Jenkins doesn't know about yet. Builds run out of order because dependencies aren't established until the jobs have run and failed. The out of order jobs fail because their should-be parents haven't run and uploaded the needed snapshots before the child builds can run.
I'm unsure if this situation is caused by a configuration issue on my end or issue with Jenkins. Is there a configuration change that I can make in order to have builds run in the correct sequence when triggered by a maven snapshot version change?
I've attached a config file typical to our jobs. Please let me know if there are any other resources I can provide.
|
|
Environment:
|
Jenkins version: 1.597
Jenkins runs on JVM: 1.7.0_72-b14 (Oracle)
Maven Integration plugin version: 2.8
Operating system: Master and nodes both Centos 6
Jenkins installed via repository: http://pkg.jenkins-ci.org/redhat
Slave nodes installed via SSH (slave node OS Centos 6)
All jobs using the Maven Project Type
Apache Subversion version 1.8.11 (r1643975)
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Joshua Scheel
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
