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

Throttle Concurrent Builds plugin doesn't work

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      One job at the end started 8 other jobs.
      All jobs belong to the same category.
      Maximum Total Concurrent Builds is set to 0 and Maximum Concurrent Builds Per Node to is set 1.
      3 jobs started simultaneously (I have 4 executors on the system)!
      Than only one was executed sequentially, as it should.
      I need to have only one job running from this category at any time!

        Attachments

          Activity

          Hide
          pgilmorepf Paul Gilmore added a comment -

          Ditto.
          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 - Ditto. 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.
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          It is impossible to diagnose the ticket without having information about Job types you are trying to Run. Please provide configuration samples. If these jobs are Pipeline ones, likely they won't work properly, see the recent changelogs

          Show
          oleg_nenashev Oleg Nenashev added a comment - It is impossible to diagnose the ticket without having information about Job types you are trying to Run. Please provide configuration samples. If these jobs are Pipeline ones, likely they won't work properly, see the recent changelogs
          Hide
          pgilmorepf Paul Gilmore added a comment -

          It's been a while, so I don't have the jobs in my Jenkins environment anymore, but the short answer is:
          Three new/empty freestyle jobs.
          Each has Windows batch command: timeout 10.
          Set the Concurrent Builds plugin as described.
          That's it.
          My jobs were as minimal as possible to ensure that it was not the fault of another plugin

          Show
          pgilmorepf Paul Gilmore added a comment - It's been a while, so I don't have the jobs in my Jenkins environment anymore, but the short answer is: Three new/empty freestyle jobs. Each has Windows batch command: timeout 10. Set the Concurrent Builds plugin as described. That's it. My jobs were as minimal as possible to ensure that it was not the fault of another plugin
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          thanks!

          Show
          oleg_nenashev Oleg Nenashev added a comment - thanks!
          Hide
          ericgojard Eric Gojard added a comment -

          Same issue here.

          Created a category, maximal total concurrent build to 0 (unlimited), maximum concurrent builds per job to 1.

          Four jobs configured to be throtlled as part of one of multiple category, using that category. I still have two of those jobs running concurrently on a node with two executors.

           

          Show
          ericgojard Eric Gojard added a comment - Same issue here. Created a category, maximal total concurrent build to 0 (unlimited), maximum concurrent builds per job to 1. Four jobs configured to be throtlled as part of one of multiple category, using that category. I still have two of those jobs running concurrently on a node with two executors.  
          Hide
          ericgojard Eric Gojard added a comment -

          (Added information : those are matrix project jobs, set to throttle on master build, and still having several master jobs running despite the expected throttle from the given category).

          Show
          ericgojard Eric Gojard added a comment - (Added information : those are matrix project jobs, set to throttle on master build, and still having several master jobs running despite the expected throttle from the given category).
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption.

          If anybody is interested, let me know

          Show
          oleg_nenashev Oleg Nenashev added a comment - Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know
          Hide
          romanz Roman Zwi added a comment -

          I think I was able to work around this by not starting all jobs at once but in 20s time intervalls instead.
          But unfortunately I can't tell gerrit trigger plugin to do so - so this workaround doesn't help me for half of my jobs...

          Show
          romanz Roman Zwi added a comment - I think I was able to work around this by not starting all jobs at once but in 20s time intervalls instead. But unfortunately I can't tell gerrit trigger plugin to do so - so this workaround doesn't help me for half of my jobs...

            People

            • Assignee:
              Unassigned
              Reporter:
              gremlm Grigoriy Milman
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: