Hi,
we have another issue with matrix and throttle-concurrents, I cannot say if it is related to this.
We have 4 executors on a node and 2 matrix projects using them. Each matrix project spawns 4 jobs. Jobs from the same matrix project can run in parallel on the same node but they conflict with jobs from other projects. So we configured the two jobs with the same category and specified to run 1 job per node. Unfortunately jobs from different projects in the same category are spawned to the same node.
We would expect to have 4 jobs from the same project... or at least 1 job from a single project and 3 free executors, not mixed project jobs.
We did the following:
Global configuration:
Category Name: mock
- Maximum Total Concurrent Builds: 0
- Maximum Concurrent Builds Per Node: 1
Job configurations:
Throttle Concurrent Builds => checked
Throttle this project as part of one or more categories => selected
- Maximum Total Concurrent Builds: 0
- Maximum Concurrent Builds Per Node: 1
- Multi-Project Throttle Category: mock
We also tried to specify the per-node global conf without any help. We also tried to set the limit for the master node (which is used as the main executor for the matrix jobs). No luck.
Note the same configuration with other non-matrix projects works fine.
Jenkins version: 1.559
Throttle Concurrent Builds Plug-in version: 1.8.2
Should I open another issue for this problem?
This issue would appear to be related:
https://issues.jenkins-ci.org/browse/JENKINS-12240
...but suggests a desire for the opposite behaviour: as many configurations of a particular job as possible should run on a node.
However, I'm sure there are just as many people who want the behaviour I'm describing, here's an example:
https://issues.jenkins-ci.org/browse/JENKINS-13619