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

Priority Sorter plugin destroys throttles (Throttle Concurrent Builds plugin)

      I have a need to use both the Throttle Concurrent Builds plugin and the Priority Sorter plugin. Say I have three jobs A, B, and C that use a throttle that allows only one concurrent execution on the master. They are all using the default priority (100). If I queue up A, then B and C, A starts running and B and C wait, throttled as they should be. But as soon as A completes, both B and C start, simultaneously. The throttle is being ignored. This worked until the Priority Sorter plugin was installed.

      I believe this issue is different from Jenkins 15090, I'm not concerned with SCM polling issues, or in this example, in the order of execution. I just need Priority Sorter to not meddle with the throttles.

      I am using:
      Jenkins 1.470
      Throttle Concurrent Builds Plugin 1.6
      Priority Sorter Plugin 1.3

          [JENKINS-16477] Priority Sorter plugin destroys throttles (Throttle Concurrent Builds plugin)

          Laura Neff created issue -
          Oleg Nenashev made changes -
          Assignee Original: bklarson [ bklarson ]
          Oleg Nenashev made changes -
          Assignee New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Component/s New: throttle-concurrents [ 15745 ]
          Labels New: concurrent-build
          Oleg Nenashev made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 147299 ] New: JNJira + In-Review [ 192326 ]
          Mark Waite made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            oleg_nenashev Oleg Nenashev
            lneff Laura Neff
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: