How to lock multiple stages of declarative Jenkins pipeline?

It should be noted that you can lock all stages in a pipeline by using the lock option:

pipeline {    agent any    options {        lock resource: 'shared_resource_lock'    }    stages {        stage('will_already_be_locked') {            steps {                echo "I am locked before I enter the stage!"            }        }        stage('will_also_be_locked') {            steps {                echo "I am still locked!"            }        }    }}

This has been fixed.

You can now lock multiples stages by grouping them in a parent stage, like this :

stage('Parent') {  options {    lock('something')  }  stages {    stage('one') {      ...    }    stage('two') {      ...    }  }}

(Don't forget you need the Lockable Resources Plugin)

The problem is that, despite the fact that declarative pipelines were technically available in beta in September, 2016, the blog post you reference (from October) is documenting scripted pipelines, not declarative (it doesn't say as much, so I feel your pain). Lockable resources hasn't been baked in as a declarative pipeline step in a way that would enable the feature you're looking for yet.

You can do:

pipeline {  agent { label 'docker' }  stages {    stage('one') {      steps {        lock('something') {          echo 'stage one'        }      }    }  }}

But you can't do:

pipeline {  agent { label 'docker' }  stages {    lock('something') {      stage('one') {        steps {          echo 'stage one'        }      }      stage('two') {        steps {          echo 'stage two'        }      }    }  }}

And you can't do:

pipeline {  agent { label 'docker' }  stages {    stage('one') {      lock('something') {        steps {          echo 'stage one'        }      }    }  }}

You could use a scripted pipeline for this use case.