Status: Open (View Workflow)
Currently lockable resource purpose is to detect overlap of resource using. It's a wonderful feature and is intuitively CI pipeline tool responsilble and removes need for external reservation dependecies.
Another external dependency is (probably) needed for telling what configuration paramaters resource have which impact build or test automation execution. That would be included to lockable resource. I suggest to give environment variables to build use from locablre resource.
Eg. configure lockable resource to have value
And using Jenkins build has e.g. environment variable
I think similar thing shall be added by this change
It will add the way to use some kind of properties for you.
In the solution is no extra filter done for that, but you can filter your resources via Groovy expression. In that case you can make also complicated filters.
BUT currently it is out of my scope, the PR need to be merged (again) and properly tested.
Any help in open-source community are welcome