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

Lockable Resource Lock with inversePrecedence=true not granting lock to newest build

    XMLWordPrintable

Details

    Description

      Lockable resources with inversePrecedence=true is not functioning correctly when used in the steps block of a Declarative Pipeline. The locked resource is locked correctly but when released it does not grant the lock to the newest build but instead the first one that requested it, as if inversePrecedence=false.

      I discovered that if you use the lock in the when block of the Declarative Pipeline the inversePrecedence behaves as expected.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              chris_carson Chris Carson
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: