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

Jobs in project fail on Maven snapshot version change

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core, (1)
      maven-plugin
    • None

      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.

          [JENKINS-27473] Jobs in project fail on Maven snapshot version change

          There are no comments yet on this issue.

            Unassigned Unassigned
            jscheel Joshua Scheel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: