[JIRA] (JENKINS-46494) Certain conditions might lock more resources than required quantity

[r.fuere...@xortex.com (JIRA)]

Title: Message Title

Reinhold Füreder commented on JENKINS-46494   Re: Certain conditions might lock more resources than required quantity I think I just stumbled over this issue as well and the change in linked pull request https://github.com/jenkinsci/lockable-resources-plugin/pull/66 actually looks reasonable/applicable at a quick naive glance... So here is my situation: Started playing around with lock based on 'label' (2 lockable resources with same label), but forgot to specify 'quantity' => so it reserved all available 2 resources (with this label) Fixing the problem by specifying 'quantity: 1' Triggering a new pipeline build with the fix, WHILE an old pipeline build WITHOUT THE FIX was still running AND was STILL LOCKING ALL 2 RESOURCES although logs claim something else: The old build (#793, 20180417-133734-revUNKNOWN) WITHOUT the fix: 13:38:43 Trying to acquire lock on [Label: PhpStorm] 13:38:43 Found 0 available resource(s). Waiting for correct amount: 2. 13:38:43 [Label: PhpStorm] is locked, waiting... 13:41:36 Lock acquired on [Label: PhpStorm] ... 13:46:29 Lock released on resource [Label: PhpStorm] The new build (#794, 20180417-134149-revUNKNOWN) WITH the fix and right (lying logs) and wrong behaviour: 13:45:36 Trying to acquire lock on [Label: PhpStorm, Quantity: 1] 13:45:36 Found 0 available resource(s). Waiting for correct amount: 1. 13:45:36 [Label: PhpStorm, Quantity: 1] is locked, waiting... 13:46:29 Lock acquired on [Label: PhpStorm, Quantity: 1] ... So the new pipeline build had to correctly wait for the releasing of the lock, but it then incorrectly locked again for all 2 resources instead of just 1: Lockable Resources view: Subsequent builds – after a coincidental pause/break that seemingly allowed to release all locks and give them completely back, instead of re-using them for queued/waiting builds – seemed to behave correctly then (and just lock 1 resource) Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.