abayer, I'm trying to lock multiple stages based on the Jenkins node on which the stages will execute. It seems like the only way to do this is using the `options` block that you specified:

stage('Parent') {
  options {
    lock("${env.NODE_NAME}")
  }
  stages {
    stage('first child') {
      ...
    }
    stage('second child') {
      ...
    }
  }
}

Unfortunately, the resource this attempts to lock is `null`:

Trying to acquire lock on [null]

It appears that this won't work because the stage's `options` directive occurs before entering the agent. The declarative pipeline syntax  documentation says: 

Inside a stage, the steps in the options directive are invoked before entering the agent or checking any when conditions.

 
Is there any way to lock multiple stages for a single env.NODE_NAME?  Ideally, other subsequent stages could still run in parallel with other builds (i.e. so limiting executors to 1 or disabling concurrent builds are not options).
 

Just wanted to +1 on rrueth's comment regarding locking multiple stages with lock named after $NODE_NAME. Pretty much in the same situation, and I'd like to know if this can be supported - either by enabling options block to execute after agent has been assigned for a given stage, or through some other means if this is not an option.

abayer do you know if this could be possible?

env is not available in options I think, but you could try getting the node name from the API:

stage('Parent') {
   options {
     lock("${currentBuild.getRawBuild().getExecutor().getOwner().getDisplayName()}")
   }
   stages {
      stage('first child') {
         ...
      }
      stage('second child') {
         ...
      }
   }
}

Hi, just wanted to add that we have the same problem where we need to lock multiple stages at once for atomicity (environment build and integration tests go together). Also, we need to parametrise the lock with the environment against which the build is done: it is ok to have parallel builds against different environments, but not against the same one.

As it looks, currently the multistage lock is available only in the options section which does not support environment parameters. Hence, it looks that we can not achieve what we need.

Bulk closing resolved issues.