Question
Tekclansolutions
IN
Last activity: 11 Jul 2025 13:03 EDT
How to Achieve Parallel Deployment to Multiple QA Environments in Deployment Manager 5.5.6
Hi Team,
We are currently using Pega Deployment Manager version 5.5.6. In our deployment pipeline, after the Dev environment, we need to deploy the same product to multiple QA environments (e.g., QA1, QA2, QA3).
At present, the deployment proceeds sequentially—QA1 environment is deployed first, and each QA environment waits for the previous one to complete. Our requirement is to configure the pipeline so that all three QA environments receive the code in parallel, immediately after the Dev stage is completed.
We are looking for guidance on how to enable parallel deployments from Dev to multiple QA environments using Deployment Manager.
Is this possible, and if so, how can it be achieved?
HCA Healthcare
US
@Pavithrap6088 In Pega Deployment Manager 5.5.6, deploying to multiple QA environments (like QA1, QA2, QA3) in parallel is not supported directly in a single pipeline, as it runs environments one after another. To achieve parallel deployment, you can create a parent pipeline that finishes after Dev and then triggers three separate child pipelines—one for each QA environment. These child pipelines can be started at the same time using REST APIs or custom tasks in the parent pipeline. Each child pipeline will deploy the same product to its respective QA environment in parallel. This setup allows you to deploy to all QA environments simultaneously after Dev, rather than waiting for one to finish before starting the next.
Tekclansolutions
IN
@Sairohith ,Thanks for the detailed explanation. I understand that Deployment Manager 5.5.6 doesn't support parallel deployments within a single pipeline stage by default. However, in our case, we would like to avoid creating multiple pipelines for each QA environment.
Our goal is to handle parallel deployments within a single pipeline, ideally from one task or stage, without branching into separate child pipelines.
Is there any recommended approach or workaround (such as using a custom task, script task, or REST integration with Azure DevOps) to achieve this within a single pipeline setup?
Appreciate any guidance or best practices for setting this up.
Thanks.