![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Attachments:
|
jenkins_matrix_trigger_error.png |
|
Components:
|
matrix-project-plugin |
|
Created:
|
30/Jan/15 4:35 PM
|
|
Description:
|
I have a Matrix project set up with a custom axis named "toolchain" with two parameters:
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.
|
|
Environment:
|
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
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Christoph Vogtländer
|
|
|
|
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.
