Hi there - Has anyone run into problems with pipeline's lock command? On a multibranch project with 2 nodes (master + 1 slave), it occasionally seems to allow two concurrent jobs to acquire the same lock. I have Jenkins 2.45 with Lockable Resources 1.11 and Pipeline 2.9.
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b55f7aa3-3a23-4e65-850d-389aed98a792%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.