[JENKINS-50260] lock step interacts badly with timeout step

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?

---
Originally reported by jekeller, imported from: lock step interacts badly with timeout step

• status: Open
  
• priority: Blocker
  
• component(s): lockable-resources-plugin
  
• resolution: Unresolved
  
• votes: 4
  
• watchers: 6
  
• imported: 20251217-081411
  

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?