Support concurrent read vs exclusive write locks

[llamahunter]

Currently, the lockable resource plugin supports exclusive write locks. It would be nice if it also supported concurrent read locks that were exclusive w.r.t. write locks.

[uwehdaub]

I would also like to see resources, that support exclusive and shared locks. And there is also e request from 2016: JENKINS-38852

[mdealer]

This would be really helpful for housekeeping jobs that need to block all executors on a node once all are free. Some sort of distinction between global and node locks would also be helpful but secondary.

[ao-apps]

This would be really helpful for housekeeping jobs that need to block all executors on a node once all are free. Some sort of distinction between global and node locks would also be helpful but secondary.

This is precisely our use-case that led us here. We have maintenance jobs (like hardlinking of dependencies via rdfind) that ideally should not run the same time as the builds. Node lock would also be important for our usage.

I know this is an old issue, but this functionality is still relevant and desired. Thank you!

[ckullabosch]

We have demand for this feature as well. In our case it is about updating a python environment on a node (writer) while multiple executors are using it (reader).