Anton Lundin

I did a really ugly workaround for the missing resourceVariable :

Did you happen to find any way of getting the resource that's locked in the current lock closure? Your workaround always returns the name of first locked resource. I'm trying to run label-based locks in parallel, so I cannot simply use getResourcesFromBuild(...)[0], but must find out the exact resource locked within current scope. Any ideas?

The hack grew quite a bit over the following days, and ended up as:

https://gist.github.com/glance-/aaa3c037757895798d4e1be5134bb843

I removed the need for extensive whitelisting by writing it as a pipeline library which later could be imported into the pipeline dsl by:
@Library("PipelineHelpers")
import PipelineHelpers.LockableResourcesHelper

We never use different locked resources in parallel so I have never needed to figure out if you can map locked resource to which block that locked it. If you ever do, please post the solution here for others to find.

We use locked resources in parallel, so the getResourcesFromBuild workaround didn't work for us.

https://github.com/jenkinsci/lockable-resources-plugin/pull/50 seems to work. (I haven't tried pull/49, but it appears to be a similar approach to the same fix.)

Anyone hoping to make use of locking a dynamic list of resources will probably find this feature (if it was ever implemented) doesn't work in v2.4 of the plugin.

So, I whipped up the following helper function which should allow you to do so:

def lockResources(listOfResources, closure) {
    if (listOfResources.size() > 1) {
        lockResources(listOfResources[1..-1], { lock(listOfResources[0]) { closure() }})
    } else {
        lock(listOfResources[0]) { closure() }
    }
}

Example usage:

def resources = ['foo', 'bar', 'baz']
lockResources(myResources, { 
    print('hello, world') 
})

Chris Dickinson Can you open a new ticket instead of commenting on a closed one (where nobody will ever see your comments, I stumbled on it by accident) if you have issues with the plugin? Anyway, locking of multiple resources is implemented since 2.3. The syntax (as generated by the snippet generator) is:

lock(extra: [[resource: 'b'], [label: 'c', quantity: 1]], resource: 'a') {
    // some block
}