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

Parallel maven jobs run out of order

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: maven-plugin
    • Labels:
    • Environment:
      Jenkins 1.635
      FreeBSD 10.2
      OpenJDK 1.8.0_60
      Google Chrome 46.0.2490.80
      maven-plugin 2.12.1
    • Similar Issues:

      Description

      Steps to reproduce:

      1) Create a new maven project and make sure it is configured to run in parallel (use my provided config.xml for reference).
      2) Execute 4 builds at the same time and wait for them to complete
      3) Run another build after the 4th one complete, notice that the next build number will be skipped!

      I enabled the hudson.maven (ALL) logger and extracted the following details in my steps to reproduce. I've attached the output to this ticket. Notice that build #36 is skipped.

      I also checked the nextBuildNumber file and noticed that it was set to 37!

        Attachments

        1. build_order.JPG
          build_order.JPG
          32 kB
        2. build_order2.JPG
          build_order2.JPG
          13 kB
        3. build_order3.JPG
          build_order3.JPG
          26 kB
        4. config.xml
          3 kB
        5. maven_log.log
          6 kB

          Issue Links

            Activity

            Hide
            ganthore Mark Austin added a comment -

            How the UI displays the info.

            Show
            ganthore Mark Austin added a comment - How the UI displays the info.
            Hide
            abayer Andrew Bayer added a comment -

            I'm guessing this is because of the weirdness of MavenModule within MavenModuleSet being actual AbstractProject objects themselves and having independent build numbering from the parent. The parent will end up setting its next build number to one higher than any of the child modules have for their highest build number. There's got to be some race condition somewhere.

            Show
            abayer Andrew Bayer added a comment - I'm guessing this is because of the weirdness of MavenModule within MavenModuleSet being actual AbstractProject objects themselves and having independent build numbering from the parent. The parent will end up setting its next build number to one higher than any of the child modules have for their highest build number. There's got to be some race condition somewhere.
            Hide
            ifernandezcalvo Ivan Fernandez Calvo added a comment -

            I could replicate it on Jenkins 1.609, 1.625 and 1.642, with a simple project with 4 submodules.
            I launch 10 build with the command

            for i in {0..9}; 
            do 
                echo $i
                curl http://127.0.0.1:8080/job/mv/build?delay=0sec
            done
            
            Show
            ifernandezcalvo Ivan Fernandez Calvo added a comment - I could replicate it on Jenkins 1.609, 1.625 and 1.642, with a simple project with 4 submodules. I launch 10 build with the command for i in {0..9}; do echo $i curl http: //127.0.0.1:8080/job/mv/build?delay=0sec done

              People

              • Assignee:
                Unassigned
                Reporter:
                ganthore Mark Austin
              • Votes:
                2 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: