[JIRA] (JENKINS-40368) Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource

[ddigt...@cloudbees.com (JIRA)]

Title: Message Title

Denys Digtiar created an issue   Jenkins / JENKINS-40368 Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource Issue Type: Bug Assignee: Unassigned Components: lockable-resources-plugin Created: 2016/Dec/12 1:11 AM Environment: lockable-resources:1.10 Labels: pipeline robustness Priority: Major Reporter: Denys Digtiar Resource lock is not always released when there is some contention over it. This can, intermittently, be reproduced by running two builds of the below pipeline concurrently. Retry will simulate inability to cancel the build which should make hard kill link to appear. Canceling the builds in turn as they acquire the lock will sometimes produce the dangling lock. retry(5) { node('linux') { lock('my-resource') { println ("running find") sh "find / -name hello.txt" } } } Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.