Issue Summary

When a deployment step starts it locks the deployment environment as part of concurrency control, but in rare situations the steps fail to unlock the environment once it is completed, preventing other builds that deploy to the same environment to start, as we cannot have more than one build at the same time deploying to the same environment.

Steps to Reproduce

This issue is not always reproducible, it happens just in rare situations.

1. Run two pipelines that deploy to the same environment. Wait for the first one to finish before running the second one.
2. The following message will be shown :

   This pipeline was paused because another pipeline was deploying to <environment>.
   

   Even though the first pipeline has already been completed.

Expected Results

When a deployment step completes, regardless of the result, it should unlock the deployment environment for future steps.

Actual Results

In rare situations, the environment is not automatically unlocked at the end of the deployment step.

Workaround

Currently, there is no known workaround for this behavior. That being said, in a situation where the deployment environment gets locked, it should be automatically unlocked 4 hours after the build step was completed.