In the freestyle/UI-based job configuration, it looks like a lock is scoped to the entire build, not one step.
The documentation for pipelines seems to imply that `lock` must be used within a `step`, but could you confirm?
I have a situation where I need to lock a resource while performing a step. I need to always cleanup that resource, so that my step works correctly.
I need to move the cleanup step to a `post / always`, so the step reports the correct exit code, but now it's outside of the lock.
I've got other jobs waiting for this resource and, based on the timing, they're trying to use the resource that this job is now cleaning up.
Well, I guess it's not valid around a `stage`.