Tobias Gruetzmacher

Interesting, while we have some tests which test "hard" kills of single Jenkins jobs, we don't have anything to check what happens when Jenkins itself dies... Which durability setting are...

@f-steff I think you confused resources and labels. A resource is always the one thing that is locked, it exists once and has an unique name (if we take the...

Superseded by #179

Does something like this work? (Minus an ugly but harmless log message) ``` lock extra: (env.BRANCH_NAME == 'master' ? [[resource: 'myResource']] : []) ```

The spurious log message is now gone in 2.6. Additionally, "dynamic" resources are now ephemeral, they get removed automatically

FWIW, this doesn't look like the way to go: `LockableResourcesManager` should be made thread-safe internally, not by sprinkling synchronized liberally all over the code. Its locking behaviour is already too...

From a cursory look, this seems quite sensible. I'll try to review more thoroughly in the coming days.

Yeah, that's the standard Jenkins CI checking for compatibility with newer Jenkins LTS versions (runs maven with `-Djenkins.version=2.222.3`) and that makes the enforcer plugin cranky. I'll try to fix it...

> We are using a lock as part of the job options, so no separate stage is shown This sounds like a feature request for [declarative pipeline](https://github.com/jenkinsci/pipeline-model-definition-plugin) - OTOH, you...

You are probably also hitting https://issues.jenkins-ci.org/browse/JENKINS-43002 ...