-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 1.635
FreeBSD 10.2
OpenJDK 1.8.0_60
Google Chrome 46.0.2490.80
maven-plugin 2.12.1
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!
- is related to
-
JENKINS-13810 Maven modules marked to wrong build when running concurrent job
-
- Reopened
-
- links to
[JENKINS-31322] Parallel maven jobs run out of order
Attachment | New: build_order3.JPG [ 31102 ] | |
Attachment | New: build_order2.JPG [ 31103 ] | |
Attachment | New: build_order.JPG [ 31104 ] |
Environment |
Original:
Jenkins 1.635 FreeBSD 10.1 OpenJDK 1.8.0_60 Google Chrome 46.0.2490.80 maven-plugin 2.12.1 |
New:
Jenkins 1.635 FreeBSD 10.2 OpenJDK 1.8.0_60 Google Chrome 46.0.2490.80 maven-plugin 2.12.1 |
Link | New: This issue is related to JENKINS-13810 [ JENKINS-13810 ] |
Workflow | Original: JNJira [ 166610 ] | New: JNJira + In-Review [ 182422 ] |
Remote Link | New: This issue links to "CloudBees Internal OSS-321 (Web Link)" [ 18914 ] |
How the UI displays the info.