-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 1.565.3 LTS
master ond Windows Server 2012, running as a Service
Linux slave, connected via ssh
custom shell script build steps
Matrix Project Plugin versions 1.3 and 1.4
I have a Matrix project set up with a custom axis named "toolchain" with two parameters:
- amd64
- arm32
In the project settings the "Execute concurrent builds if necessary" is off.
Nonetheless, under certain conditions concurrent builds are triggered and a build is run in a "@2" directory.
Steps to reproduce:
- trigger a new build, a trigger build is started on the master (without consuming a build executor), two builds are started on the slave (for arm32 and amd64)
Info: the build for axis arm32 is much quicker than the build for amd64 - trigger a second build -> build is now in the queue waiting for the first build to finish
- when the sub build for axis arm32 finishes, the next build is executed right away without waiting for the amd64 build to be finished
- the second arm32 build will run in a "@2" folder like a concurrent build would
- the build for the second amd64 axis is queued correctly, waiting for the first build to finish
When triggering a second build after the arm32 has already finished everything works fine -> the whole build for both axes will stay in the queue until the amd64 axis build finishes.