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

Throttle Concurrent Builds on scheduled builds at the same time

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Number of Executors: 2

      If two jobs are configured as shown below, both jobs are started and executed at the same time. What i expected is that one of them starts and the second one is in the build queue.
      The same behavior occurs, if they are triggered by a post-commit hook.
      The real use case is triggered by a post-commit hook, the example depicted below is only to reproduce this behavior.

      Cofiguration of job A:
      Throttle Concurrent Builds

      • Throttle this project as part of one or more categories
      • Maximum Total Concurrent Builds: 1
      • Maximum Concurrent Builds Per Node: 1
      • Multi-Project Throttle Category: Catergory_1

      Build periodically
      Schedule 30 11 * * *

      Configuration of job B:
      Throttle Concurrent Builds

      • Throttle this project as part of one or more categories
      • Maximum Total Concurrent Builds: 1
      • Maximum Concurrent Builds Per Node: 1
      • Multi-Project Throttle Category: Catergory_1

      Build periodically
      Schedule 30 11 * * *

        Attachments

          Activity

          tsauter Thomas Sauter created issue -
          rtyler R. Tyler Croy made changes -
          Field Original Value New Value
          Workflow JNJira [ 173668 ] JNJira + In-Review [ 185274 ]
          tsauter Thomas Sauter made changes -
          Description Number of Executors: 2

          If two jobs are configured as shown below, both jobs are started and executed at the same time. What i expected is that one of them starts and the second one is in the build queue.
          The same behavior occurs, if they are triggered by a post-commit hook.

          Cofiguration of job A:
          *Throttle Concurrent Builds*
          * Throttle this project as part of one or more categories
          * Maximum Total Concurrent Builds: 1
          * Maximum Concurrent Builds Per Node: 1
          * Multi-Project Throttle Category: Catergory_1

          *Build periodically*
          Schedule 30 11 * * *

          Configuration of job B:
          *Throttle Concurrent Builds*
          * Throttle this project as part of one or more categories
          * Maximum Total Concurrent Builds: 1
          * Maximum Concurrent Builds Per Node: 1
          * Multi-Project Throttle Category: Catergory_1

          *Build periodically*
          Schedule 30 11 * * *
          Number of Executors: 2

          If two jobs are configured as shown below, both jobs are started and executed at the same time. What i expected is that one of them starts and the second one is in the build queue.
          The same behavior occurs, if they are triggered by a post-commit hook.
          The real use case is triggered by a post-commit hook, the example depicted below is only to reproduce this behavior.

          Cofiguration of job A:
          *Throttle Concurrent Builds*
          * Throttle this project as part of one or more categories
          * Maximum Total Concurrent Builds: 1
          * Maximum Concurrent Builds Per Node: 1
          * Multi-Project Throttle Category: Catergory_1

          *Build periodically*
          Schedule 30 11 * * *

          Configuration of job B:
          *Throttle Concurrent Builds*
          * Throttle this project as part of one or more categories
          * Maximum Total Concurrent Builds: 1
          * Maximum Concurrent Builds Per Node: 1
          * Multi-Project Throttle Category: Catergory_1

          *Build periodically*
          Schedule 30 11 * * *
          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
          oleg_nenashev Oleg Nenashev made changes -
          Assignee Oleg Nenashev [ oleg_nenashev ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            tsauter Thomas Sauter
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: