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

lock step in Pipeline should allow creation of implicit per-job locks

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When using a lock step in a Pipeline it is possible to name a globally defined resource and lock it. However, in order to use lock to institute concurrency within a job, Pipeline would need to create an implicit (ephemeral) resource that prevents other jobs from entering the defined lock step.

      There has been some discussion about how this would be implemented to avoid name collisions among different jobs.

        Attachments

          Activity

          Hide
          nharniman Nigel Harniman added a comment -

          Should this say:

          that prevents other builds of this job from entering

          Show
          nharniman Nigel Harniman added a comment - Should this say: that prevents other builds of this job from entering
          Hide
          jglick Jesse Glick added a comment -

          As previously noted, I have yet to see a compelling example of when you would actually want this behavior, so I suggest this be put on hold until there is one.

          Show
          jglick Jesse Glick added a comment - As previously noted, I have yet to see a compelling example of when you would actually want this behavior, so I suggest this be put on hold until there is one.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            hrmpw Patrick Wolf
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated: