Details

    • Type: New Feature
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: pipeline
    • Labels:
      None
    • Similar Issues:

      Description

      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!

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

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

            Show
            jglick Jesse Glick added a comment - stage is not designed for this use case; a separate step would be more appropriate.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: