# Optimization of Pipeline Lock Strategy for Parallel Environment Deployments

**URL:** <https://community.jenkins.io/t/optimization-of-pipeline-lock-strategy-for-parallel-environment-deployments/36888>\
**Category:** Using Jenkins\
**Created:** [May 8, 2026, 3:08pm UTC](https://community.jenkins.io/t/optimization-of-pipeline-lock-strategy-for-parallel-environment-deployments/36888 "2026-05-08T15:08:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hari21225](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/hari21225/32/21279_2.png) [@Hari21225](https://community.jenkins.io/u/Hari21225)\
**Post date:** [May 8, 2026, 3:08pm UTC](https://community.jenkins.io/t/optimization-of-pipeline-lock-strategy-for-parallel-environment-deployments/36888/1 "2026-05-08T15:08:07Z")

</div>

I am managing a Groovy-based Jenkins Scripted Pipeline for a microservice that deploys to multiple environments (DEV, ACC, PROD). We currently use a global lock at the start of the pipeline logic to prevent concurrent execution.

- **Jenkins Version:** 2.319.1

- **Key Plugin:** Lockable Resources Plugin

- **Environment:** Kubernetes-based agents (podTemplate)

**Current Implementation:** Currently, our pipeline is wrapped in a global lock like this:

---

<div class="post-metadata">

**Author:** ![mawinter69](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/mawinter69/32/1625_2.png) [@mawinter69](https://community.jenkins.io/u/mawinter69)\
**Post date:** [May 8, 2026, 5:11pm UTC](https://community.jenkins.io/t/optimization-of-pipeline-lock-strategy-for-parallel-environment-deployments/36888/2 "2026-05-08T17:11:10Z")

</div>

You missed to add the pipeline code