Pipeline locking: Ensure only one instance of a GoCD pipeline can run at the same time

If a pipeline is locked then GoCD will not allow any other instance of that pipeline to be scheduled until the currently running one has been completed.

To enable locking from the Config UI, navigate to the Pipeline Settings section of a pipeline. There are three options for locking:

This option enables a single instance of the pipeline to run at a time. The pipeline is locked when it starts and it remains locked if it fails. The pipeline is unlocked if it reaches the last stage (even if it fails). The pipeline is not unlocked if it reaches a manual stage. If a pipeline is locked, it will not allow any new instances to run, unless it is unlocked, either manually or through the API.

This is the default behavior. Multiple instances of a pipeline can run simultaneously.

Controlling locking behavior from the config XML

Also see the configuration reference.