-
Bug
-
Resolution: Duplicate
-
Major
-
None
I know this is probably going to be in opposition as much as it's for which suggests an optional behaviour however...
I would like (optionally of course since just as many people seem to want the opposite) for all of the children of a multiconfiguration job to contribute to the count of jobs in terms of throttling.
That is, if I set a category of "foo" and set it's throttle limit at 10 and have a multiconfiguration job that ends up spawning 7 child jobs (i.e. valid matrix intersections) I would like for those 7 child jobs to use up 7 of the 10 available "slots" for that category.
- duplicates
-
JENKINS-13619 Add ability to throttle number of concurrent builds of matrix configurations per node
-
- Resolved
-
[JENKINS-20574] throttling needs to account for all child jobs of a multiconfiguration job
Leif Hedstrom
added a comment - Going through some Jira's, I suspect this one is a dupe of JENKINS-19986 ?
Leif Hedstrom
added a comment - Going through some Jira's, I suspect this one is a dupe of JENKINS-19986 ? 
Vlad Dovlekaev
added a comment - Having the same issue here. Voting to fix/add this feature. Major blocker for us as we have a limited shared resources for very large matrix job and would like to throttle the child jobs as well.
Vlad Dovlekaev
added a comment - Having the same issue here. Voting to fix/add this feature. Major blocker for us as we have a limited shared resources for very large matrix job and would like to throttle the child jobs as well. 
I'm having the same "issue" as well. Is there any hope of this feature being added? Is there some other solution I should look at ? I'm using the Matrix Project plugin as well, and I really need to limit each node to have only one sub-job (matrix intersection) running (they stomp on each other). But I also want to have > 1 executor per node.