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

mixing inversePrecedence true/false gives unexpected results.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • lockable-resources-plugin
    • None
    • lockable-resources 1.11
      jenkins 2.32.1
      workflow-aggregator 2.4

      As far as I understad it based on :
      https://github.com/jenkinsci/lockable-resources-plugin/blob/lockable-resources-1.11/src/main/java/org/jenkins/plugins/lockableresources/LockableResourcesManager.java#L288

      Its actually the releasing job who queues up the next job. Also the controlling inversePrecedence comes from the job thats releasing the lock, not the job who is getting the resource from the last job.

          [JENKINS-41070] mixing inversePrecedence true/false gives unexpected results.

          There are no comments yet on this issue.

            Unassigned Unassigned
            glance Anton Lundin
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: