Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
We have a limit on the number of licenses we can use concurrently. Before pipeline as code we could use the throttle to limit the number of jobs to 16.
With pipeline as code and 2.0 of the plugin we cannot limit jobs unless we create the jobs and trigger in parallel.
Is there any intention to make the lateste plugin work in the same way as before without having to do parallel jobs
Attachments
Activity
The new documentation is now clear on the use of throttle for pipelines.
Joachim Hagege
added a comment - Hi, any update on support of declarative pipeline flows ?
Thanks 
Simon K
added a comment - Hi, we switched to the lock-Plugin for this use case:
https://wiki.jenkins.io/display/JENKINS/Lockable+Resources+Plugin
Worked as aspected
Simon K
added a comment - Hi, we switched to the lock-Plugin for this use case:
https://wiki.jenkins.io/display/JENKINS/Lockable+Resources+Plugin
Worked as aspected Lockable resources solves some use cases in declarative pipelines, but not all.
I want to limit builds of a declarative pipeline project to one build per node. I can't achieve this.
The documentation in "Example 3: Throttling of declarative pipelines" is lacking/misguiding. I've tested, and it has no throttling effect on a single declarative Pipeline job. Does it only throttle between jobs using same category? (And in that case, are different branches in a multi-branch pipeline considered different jobs?) IMHO, that feature is not as useful as being able to throttle on the same job.
Code changed in jenkins
User: Oleg Nenashev
Path:
README.md
http://jenkins-ci.org/commit/throttle-concurrent-builds-plugin/7c61f6119c67ffb046bcf3afb596671b12011bd8
Log:
Merge pull request #49 from oleg-nenashev/docs/JENKINS-44411-clarify-throttle-step
JENKINS-44411 - Extend documentation to clarify throttle() behavior
Compare: https://github.com/jenkinsci/throttle-concurrent-builds-plugin/compare/1497858da1f6...7c61f6119c67