-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
I have a job which takes a lock {} inside of a timeout {} block.
If the timeout expires, then the lock {} is not freed, which results in future taking of the lock becoming a deadlock.
It seems like timeout {} should properly free the lock when forcing an exit from the lock() step? Is this just a bad pipeline/workflow pattern?
[JENKINS-50260] lock step interacts badly with timeout step
Component/s | Original: workflow-basic-steps-plugin [ 21712 ] |