When you must deploy the changes made to the branches continuously to the Release pipeline to make the changes available for testing and releasing to Production, you can trigger a Deployment pipeline through a Merge pipeline. With the help of the Trigger Deployment task, you can achieve the continuous release of your application on a successful merge.
The Trigger Deployment task requires the Pipeline ID for the target pipeline for which it creates a deployment.
To configure Continuous Delivery (CD), include the Trigger Deployment task to trigger a deployment at the end of the Merge pipeline, which starts a Release pipeline for your application.
You can also use the Trigger deployment task on the Deployment pipeline.
Triggering a deployment on successful merge
You can start another pipeline by adding the Trigger deployment task to a stage in
your current pipeline. By starting another pipeline from a current pipeline, you can add
more stages to your pipeline.
To add the Trigger deployment task to a stage in your
pipeline, perform the following steps:
Do one of the following actions:
Click a task, click the More icon, and then click
either Add task above or Add task
below.
Click Add task in the stage.
In the Task list, click Trigger
deployment.
In the Application name field, press the Down arrow key,
and then select the application that you want to deploy.
In the Pipeline name field, press the Down arrow key
and, then select the pipeline that you want to start.
If you want to deploy the artifact that you are deploying in the current
pipeline, select the Deploy current artifact check box.
Otherwise, a new application is deployed on the pipeline.
Click Submit.
When you configure a Merge pipeline with the Trigger Deployment task, specify the Pipeline ID for the target application, as shown in the following figure:
Configuring a trigger deployment task with the target pipeline's ID.
Check your knowledge through the following interaction.
Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.
