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

Use stage as a resource lock

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Duplicate
    • Icon: Minor Minor
    • pipeline
    • None

      My use case is users launching multiple jobs that use a lot of server bandwidth, so I would prefer to do something that limits the number of stages running concurrently similar to:

      stage 'start'
stage name: 'bandwidth-hog', concurrency: 5, resourceLock: true
//bandwidth hogging code
stage 'finish'

      However, I can't have newer jobs pre-empt older jobs, they should just be queued up. Of course, this could be a new step as well. Hopefully this helps others as well!

          [JENKINS-30757] Use stage as a resource lock

          Anshu Arya created issue -
          Anshu Arya made changes -
          Link New: This issue is related to JENKINS-27039 [ JENKINS-27039 ]
          Anshu Arya made changes -
          Description Original: My use case is users launching multiple jobs that use a lot of server bandwidth, so I would prefer to do something that limits the number of stages running concurrently similar to:

          {code}
          stage 'start'
          stage name: 'bandwidth-hog', concurrency: 5, resourceLock: true
          //bandwidth hogging code
          stage 'finish'
          {code}

          It would be useful if newer jobs did not pre-empt older jobs, but just queued up. Of course, this could be a new step as well. Hopefully this helps others as well!           		New: My use case is users launching multiple jobs that use a lot of server bandwidth, so I would prefer to do something that limits the number of stages running concurrently similar to:

          {code}
          stage 'start'
          stage name: 'bandwidth-hog', concurrency: 5, resourceLock: true
          //bandwidth hogging code
          stage 'finish'
          {code}

          However, I can't have newer jobs pre-empt older jobs, they should just be queued up. Of course, this could be a new step as well. Hopefully this helps others as well!

          Jesse Glick added a comment -

          stage is not designed for this use case; a separate step would be more appropriate.

          Jesse Glick added a comment - stage is not designed for this use case; a separate step would be more appropriate.
          Jesse Glick made changes -
          Link New: This issue duplicates JENKINS-30269 [ JENKINS-30269 ]
          Jesse Glick made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 165884 ] New: JNJira + In-Review [ 197841 ]
          Andrew Bayer made changes -
          Component/s New: pipeline-general [ 21692 ]
          Andrew Bayer made changes -
          Component/s Original: workflow-plugin [ 18820 ]

            jglick Jesse Glick
            anshuarya Anshu Arya
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: