Parallel releases

Parallel releases run multiple non-conflicting selective service releases at once in the same environment, with queuing or state-lock handling.

Parallel Release feature enables simultaneous execution of multiple Selective Releases for service resources within the same environment, enhancing deployment flexibility and speed.

By allowing parallel execution of non-conflicting releases, this feature minimises deployment time while efficiently handling conflicts through queuing or error management.

Note: A release parked for approval blocks parallel execution. See Release Approval.

How to Enable Parallel Releases?

Navigate to Settings > General to view the Control Plane settings.
Set Enable Parallel Releases to true (this is set to false by default).
Specify the Maximum Parallel Releases that can be executed across the Control Plane.
Note: The default value for Maximum Parallel Releases is set to 10.
Click Save Changes.

You have successfully enabled the parallel release.

How to Use Parallel Releases?

Triggering Releases

Perform multiple Selective Releases as usual. The Control Plane automatically executes non-conflicting releases in parallel.

Execution Logic

Non-conflicting releases run in parallel.
Conflicting releases are queued or fail with a state lock error, requiring manual re-triggering.

Conflict Scenarios & Error Handling

Parallel execution supports Selective Updates and Selective Create/Delete unless they target the same resource.
Conflicting releases involving shared resources or Selective Create/Delete result in queuing or state lock errors.
Re-trigger failed releases after resolving conflicts for smooth deployment.

Rollback Support

Rollbacks are supported, but a release with refresh enabled may be necessary to fully restore the system.