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

Throttle Concurrent Builds plugin doesn't appear to work

    Details

    • Similar Issues:

      Description

      I just installed this today to try and avoid some issues I have with locks & latches. I have some multi-configuration jobs. I want to allow multiple jobs to run at the same time, but only 1 job of a given category to run per node. This sounds exactly like what the plugin was written for. So I went into my configuration and created a category and set Maximum Total Concurrent Builds to 0 and Maximum Concurrent Builds Per Node to 1. I then went to all of my jobs and assigned them to this category and checked the radio button for throttle as part of one or more categories.

      I then manually started two jobs from the same category to see if one waited for the other. It didn't work. Both jobs started on the same node. I also tried settings Maximum Concurrent Builds Per Node in the job itself to 1 and that didn't help either.

      What am I missing about this configuration?

        Attachments

          Issue Links

            Activity

            Hide
            iturchenko Igor Turchenko added a comment -

            Sorry, I was wrong. I forgot to allow concurrent builds for job itself.

            Show
            iturchenko Igor Turchenko added a comment - Sorry, I was wrong. I forgot to allow concurrent builds for job itself.
            Hide
            dkaelbling David Kaelbling added a comment -

            I'm also unable to throttle even very simple matrix jobs, running Jenkins 1.565 and version 1.8.2 of the plugin. The job setup is:

            • Throttle this project alone
            • Maximum total concurrent builds: 0
            • Maximum concurrent builds per node: 1
            • One user-defined axis

            When I launch it no throttling is done – every available executor starts processing one of the configurations.

            I tried throttling by category (changing the project limits 0) and got the same behavior, both for generic limits and node-specific category limits.

            How can I help debug this?

            Show
            dkaelbling David Kaelbling added a comment - I'm also unable to throttle even very simple matrix jobs, running Jenkins 1.565 and version 1.8.2 of the plugin. The job setup is: Throttle this project alone Maximum total concurrent builds: 0 Maximum concurrent builds per node: 1 One user-defined axis When I launch it no throttling is done – every available executor starts processing one of the configurations. I tried throttling by category (changing the project limits 0) and got the same behavior, both for generic limits and node-specific category limits. How can I help debug this?
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            See JENKINS-13619 for all issues related to MATRIX jobs.
            The new release of the plugin will provide throttling of matrix configurations in "Categories" mode at least

            Show
            oleg_nenashev Oleg Nenashev added a comment - See JENKINS-13619 for all issues related to MATRIX jobs. The new release of the plugin will provide throttling of matrix configurations in "Categories" mode at least
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Closing as a duplicate of JENKINS-13619 (fixed in throttle-concurrents-1.8.3)

            Show
            oleg_nenashev Oleg Nenashev added a comment - Closing as a duplicate of JENKINS-13619 (fixed in throttle-concurrents-1.8.3)
            Hide
            pgilmorepf Paul Gilmore added a comment -

            I think this issue has returned.
            I'm using Jenkins 2.32.1
            I have 10 executors on my Jenkins installation
            I set up 3 jobs, which all have these TCB options set:
            Throttle this project as part of one or more categories (set)
            Maximum Total Concurrent Builds = 1
            Maximum Concurrent Builds Per Node = 1
            List of parameters to check: Expensive

            If I queue up all 3 jobs, they all three run simultaneously. I expected them to block each other.

            Show
            pgilmorepf Paul Gilmore added a comment - I think this issue has returned. I'm using Jenkins 2.32.1 I have 10 executors on my Jenkins installation I set up 3 jobs, which all have these TCB options set: Throttle this project as part of one or more categories (set) Maximum Total Concurrent Builds = 1 Maximum Concurrent Builds Per Node = 1 List of parameters to check: Expensive If I queue up all 3 jobs, they all three run simultaneously. I expected them to block each other.

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                jpschewe jpschewe
              • Votes:
                8 Vote for this issue
                Watchers:
                24 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: