At present there is no explicit support for either locking or unlocking resources in this fashion, but you can accomplish it by calling the appropriate APIs directly from the flow DSL as it is not currently sandboxed.
I would not necessarily expect the lockable resources plugin to ever explicitly support this behaviour because it more focused on managing locks prior to builds even starting. Is it possible that the Exclusion Plugin is more suited to what you are trying to do? Again there is no explicit support between these two plugins, but you may be able to accomplish what you need via direct API calls and the plugin is intended to lock/unlock during the course of a build.
At present there is no explicit support for either locking or unlocking resources in this fashion, but you can accomplish it by calling the appropriate APIs directly from the flow DSL as it is not currently sandboxed.
I would not necessarily expect the lockable resources plugin to ever explicitly support this behaviour because it more focused on managing locks prior to builds even starting. Is it possible that the Exclusion Plugin is more suited to what you are trying to do? Again there is no explicit support between these two plugins, but you may be able to accomplish what you need via direct API calls and the plugin is intended to lock/unlock during the course of a build.