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

Throttling based on parameters does not work with Pipeline jobs

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      2.2

      Description

      Configuration

      1. Pipeline job with parameters
      2. Execute concurrent builds if necessary: true
      3. Throttle Concurrent Builds: true
      4. Prevent multiple jobs with identical parameters from running concurrently: true

      Notes

      • Job parameters are defined as part of the pipeline setup with the properties command
      • This is also an issue when properties are not defined as part of the pipeline setup, and are configured through the UI directly

      Problem

      When throttling based on one of the job's parameters, the plugin does not prevent multiple builds from running concurrently when the defined parameter is the same.

        Attachments

          Issue Links

            Activity

            Hide
            basil Basil Crow added a comment -

            Released in 2.2.

            Show
            basil Basil Crow added a comment - Released in 2.2 .
            Hide
            basil Basil Crow added a comment -
            Show
            basil Basil Crow added a comment - Fixed in jenkinsci/throttle-concurrent-builds-plugin#117 .
            Hide
            francob Franco Bladilo added a comment -

            Having the same issues not being able to throttle pipeline jobs based on parameters, has this received any attention/help/updates? This is causing a lot of pain on our internal CI. Running Jenkins jenkins-2.222.1 with latest TCB.

            Show
            francob Franco Bladilo added a comment - Having the same issues not being able to throttle pipeline jobs based on parameters, has this received any attention/help/updates? This is causing a lot of pain on our internal CI. Running Jenkins jenkins-2.222.1 with latest TCB.
            Hide
            shezaan Sherabi GuessWhat added a comment - - edited

            We are having the same issue.
            1. Uncheck "Do not allow concurrent builds"
            2. Check "Throttle concurrent builds"
                 -> Check "Prevent multiple jobs with identical parameters from running concurrently"

            Below is Pipeline as code for the above steps:

            // disableConcurrentBuilds(), --> Note concurrency is enabled since this line is commented out.
            [$class: 'ThrottleJobProperty', categories: [], limitOneJobWithMatchingParams: true, maxConcurrentPerNode: 0, maxConcurrentTotal: 0, paramsToUseForLimit: '', throttleEnabled: true, throttleOption: 'project']

            Show
            shezaan Sherabi GuessWhat added a comment - - edited We are having the same issue. 1. Uncheck "Do not allow concurrent builds" 2. Check "Throttle concurrent builds"      -> Check "Prevent multiple jobs with identical parameters from running concurrently" Below is Pipeline as code for the above steps: // disableConcurrentBuilds(), --> Note concurrency is enabled since this line is commented out. [$class: 'ThrottleJobProperty', categories: [], limitOneJobWithMatchingParams: true , maxConcurrentPerNode: 0, maxConcurrentTotal: 0, paramsToUseForLimit: '', throttleEnabled: true , throttleOption: 'project']
            Hide
            dannyg Danny Gueta added a comment -

            +1, any update on this ? we've used this plugin in the past but once we moved to pipelines its not working anymore, can't limit by parameters. 

            Show
            dannyg Danny Gueta added a comment - +1, any update on this ? we've used this plugin in the past but once we moved to pipelines its not working anymore, can't limit by parameters. 

              People

              Assignee:
              basil Basil Crow
              Reporter:
              alunsford Aaron Lunsford
              Votes:
              13 Vote for this issue
              Watchers:
              18 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: