Add option to filter build with matching when counting current running jobs

[nmorey]

Note: Job in the same category but with no parameters are not counted either

Signed-off-by: Nicolas Morey-Chaisemartin [email protected]

In our current CI at Kalray, we often have very long integration queues (build are very long and we have 30 people committing a lot).
To accelerate that, we want to run several integration (same project) in parallel. But it is only safe if these run do not target the same integration branch.
The branch being one of the parameters, I added a setting to the throttle plugin so we don't count the overll number of task but only the task whom parameter (specified in the throttle config) match.

This doesn't apply directly on 1.8.1 as I've been told it's buggy and is not written to be applied straight away.
If the feature seems interesting to other, it can be probably cleaned up and contributed. If not, I'm open to feedback on better ways to do this.

[cloudbees-pull-request-builder]

plugins » throttle-concurrent-builds-plugin #19 FAILURE
Looks like there's a problem with this pull request

[oleg-nenashev]

This way won't work in general, because everybody has his own categorization approach.

I suppose we need to add a CategoryProvider extension, where users will be able to implement their own categories. Unfortunately, it would be quite difficult to retain the performance in such approach.

[nmorey]

I guess it's very specific to what we need.
The easiest way, I guess, would be to be able to generate a resource list associated specifically to the run (thus have access to its parameters and all the necessary info) and not the project.
Which doesn't seem possible unless I missed something

[jenkinsadmin]

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

[oleg-nenashev]

Changes in pom.xml should be removed