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

Throttle Concurrent Builds doesn't work when builds are in cloudbees folders

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • throttle-concurrent-builds-plugin
    • jenkins 1.585, throttle concurrent builds plugin 1.8.4, cloudbees folder 4.6.1

      We recently organized our builds into folders, and we noticed that our concurrent build throttling wasn't working. It doesn't work between folders or for builds within the same folder. It only works when it's in the main workspace.

          [JENKINS-25326] Throttle Concurrent Builds doesn't work when builds are in cloudbees folders

          Gail Terman created issue -
          Jesse Glick made changes -
          Component/s Original: cloudbees-folder [ 18137 ]
          Labels New: folders
          Jesse Glick made changes -
          Assignee Original: Jesse Glick [ jglick ] New: Andrew Bayer [ abayer ]

          Daniel Beck added a comment - - edited

          I confirm the reported behavior on 1.586, 1.8.4, and Folders 4.6.1.

          Set up a category 'foo' with 1 maximum concurrent build.
          Create two freestyle jobs JENKINS-25326-one and JENKINS-25326-two in the same folder 'experiments'. Enable throttling and assign the category 'foo'. Make both of them 'sleep 30' in a shell build step.
          Trigger both of them.
          They will run in parallel.

          Daniel Beck added a comment - - edited I confirm the reported behavior on 1.586, 1.8.4, and Folders 4.6.1. Set up a category 'foo' with 1 maximum concurrent build. Create two freestyle jobs JENKINS-25326 -one and JENKINS-25326 -two in the same folder 'experiments'. Enable throttling and assign the category 'foo'. Make both of them 'sleep 30' in a shell build step. Trigger both of them. They will run in parallel.

          Daniel Beck added a comment - - edited

          There's something weird going on. It seems to only occur with newly created jobs. Jobs that existed when Jenkins was last started are not affected.

          Daniel Beck added a comment - - edited There's something weird going on. It seems to only occur with newly created jobs. Jobs that existed when Jenkins was last started are not affected.

          Oleg Nenashev added a comment -

          No response...
          AFAIK, it has been fixed in 1.8.2

          Oleg Nenashev added a comment - No response... AFAIK, it has been fixed in 1.8.2
          Oleg Nenashev made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Daniel Beck added a comment -

          Oleg: I confirmed the report and added additional information. There's nothing to respond to.

          Daniel Beck added a comment - Oleg: I confirmed the report and added additional information. There's nothing to respond to.
          Daniel Beck made changes -
          Resolution Original: Cannot Reproduce [ 5 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          Oleg Nenashev added a comment -

          Yes, my bad. I was going to close JENKINS-22049, but selected a wrong tab in the browser.
          I'm investigating the issue now

          Oleg Nenashev added a comment - Yes, my bad. I was going to close JENKINS-22049 , but selected a wrong tab in the browser. I'm investigating the issue now

            ikedam ikedam
            gailterman Gail Terman
            Votes:
            3 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: