Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44411

Support throttling of blocks without node() in the throttle() step

      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

          [JENKINS-44411] Support throttling of blocks without node() in the throttle() step

          Oleg Nenashev added a comment -

          Created https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/49 with documentation improvements. rob_squire I will appreciate feedback in the pull request.

          Regarding this issue, I am going to convert it to RFE

          Oleg Nenashev added a comment - Created https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/49 with documentation improvements. rob_squire I will appreciate feedback in the pull request. Regarding this issue, I am going to convert it to RFE

          Robert Squire added a comment -

          Ok happy to give feedback

          Robert Squire added a comment - Ok happy to give feedback

          Robert Squire added a comment -

          In a pipeline job we do sometimes have two build stages one might use the arm license and another build in the same pipeline might use msbuild to build a host exe. It would be good to be able to limit the arm build but allow msbuild builds to run without any throttling.

          Robert Squire added a comment - In a pipeline job we do sometimes have two build stages one might use the arm license and another build in the same pipeline might use msbuild to build a host exe. It would be good to be able to limit the arm build but allow msbuild builds to run without any throttling.

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          README.md
          http://jenkins-ci.org/commit/throttle-concurrent-builds-plugin/ad8072a541fcacc0175b6468092e19392e0b91e4
          Log:
          JENKINS-44411 - Extend documentation to clarify throttle() behavior and supported use-cases

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: README.md http://jenkins-ci.org/commit/throttle-concurrent-builds-plugin/ad8072a541fcacc0175b6468092e19392e0b91e4 Log: JENKINS-44411 - Extend documentation to clarify throttle() behavior and supported use-cases

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          README.md
          http://jenkins-ci.org/commit/throttle-concurrent-builds-plugin/68f1f3fa1cd3d96ae71675008bbff0e4ba61ab52
          Log:
          JENKINS-44411 - Drop the confusing sentence

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: README.md http://jenkins-ci.org/commit/throttle-concurrent-builds-plugin/68f1f3fa1cd3d96ae71675008bbff0e4ba61ab52 Log: JENKINS-44411 - Drop the confusing sentence

          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

          SCM/JIRA link daemon added a comment - 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

          Robert Squire added a comment -

          The new documentation is now clear on the use of throttle for pipelines.

          Robert Squire added a comment - The new documentation is now clear on the use of throttle for pipelines.

          Hi, any update on support of declarative pipeline flows ? 
          Thanks

          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

          Marcus Philip added a comment - - edited

          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.

          Marcus Philip added a comment - - edited 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.

            Unassigned Unassigned
            rob_squire Robert Squire
            Votes:
            12 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: