-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
master and 9 slaves all running SUSE Linux.
Jenkins 1.480.2
throttle-concurrents: 1.7.2
I've set up two Multi-Project Throttle Categories, filesystem and postgres, both with maximum total concurrent builds of 0 and maximum concurrent builds per node of 1.
This is because only one job that uses these categories can run on a host at once, if two try, they'll stomp all over each other.
So, I've configured two jobs, both matrix jobs, and both configured with "Throttle Concurrent Builds" checked, "throttle this projects as part of one or more catogories" checked and both the categories defined above checked.
However, when a node has more than one executor, I'll frequently see multiple configurations from the matrix being run on the same node at the same time. Sure enough, they stomp all over each other.
- duplicates
-
JENKINS-13619 Add ability to throttle number of concurrent builds of matrix configurations per node
-
- Resolved
-
[JENKINS-16521] Multi-Project Throttle Categories don't work with Matrix jobs
Chris Withers
created issue -
Chris Withers
added a comment - I've just verified that this is a regression in 1.7.2.
1.7.1 behaves as expected, so I'll downgrade to that as a workaround...
Chris Withers
added a comment - I've just verified that this is a regression in 1.7.2.
1.7.1 behaves as expected, so I'll downgrade to that as a workaround... Chris Withers
added a comment - https://issues.jenkins-ci.org/browse/JENKINS-16552 is a duplicate of this issue.
Chris Withers
added a comment - https://issues.jenkins-ci.org/browse/JENKINS-16552 is a duplicate of this issue. 
Wael Darwich
added a comment - I tried 1.7.1 but had the same unwanted behaviour as 1.7.2! Chris Withers
added a comment - I'm also now seeing this on 1.7.1 with 1.480.3 :-/ Same here. Version 1.72 and 1.513 of Jenkins. Is this, https://issues.jenkins-ci.org/browse/JENKINS-12240, supposed to fix it? It is included in version 1.72 according to commits.
Update: Cloned tag 1.7.1 and installed and it seems to work using Category.
Created a "Matrix-job" category using "Maximum Total Concurrent Build = 4" and "Maximum Concurrent Builds Per Node = 4". The job itself is configured with "Maximum Concurrent Builds Per Node = 1" and "Maximum Total Concurrent Build = 4". I am not using any slaves though.
Chris Withers
added a comment - Yeah, I thought it was working, and then found overlapping matrix child jobs on some slave nodes.
So, have to default to one executor per slave, which means those slaves can't be used for any other jobs (that don't use the throttled resources), which is a waste 
Chris Withers
added a comment - Yeah, I thought it was working, and then found overlapping matrix child jobs on some slave nodes.
So, have to default to one executor per slave, which means those slaves can't be used for any other jobs (that don't use the throttled resources), which is a waste 
hiteswar kumar
added a comment - Hi Andrew(Abayer),
Can you please fix this and release 1.7.3 fast.
or if any one has already done fix..please do the pull request to get it merged.
hiteswar kumar
added a comment - Hi Andrew(Abayer),
Can you please fix this and release 1.7.3 fast.
or if any one has already done fix..please do the pull request to get it merged.
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