To add a pipeline, from the Deployment Manager portal, perform the following steps:

1. Click Pipelines.
2. On the top-right of the portal, click New .
3. Select Update pipeline.

   

   

   Pipeline templates drive the necessary information to complete the creation of a pipeline. For more information, see Pipeline templates.
   Note: If you choose to navigate away from any of the pipeline creation screens, save your configuration. If you do not save the configurations, you lose your progress. Continue below to add application environment and pipeline model details.

To configure application details, perform the following steps:

Application packaging environment

1. In the Pipeline name field, enter a name for the pipeline.
2. In the Application packaging environment field, specify the environment URL for the application package location.
3. In the Authentication profile field, select or enter the authentication profile to connect to the application packaging environment.
   Note: Pega Cloud auto-detects the application packaging environment with the staging clone environment provisioned for update validation. Validate the accuracy of this URL.

Go-no-Go approver

4. In the Approver dropdown list, select the Deployment Manager user to promote the update to environments and confirm that the platform update is complete.

   

   

To strengthen the decision to update the production environment, Deployment Manager provides two instances to customers These two instances are:

• The Staging-Clone environment is the updated, cloned staging-environment where you make update fixes. On Pega Cloud services, the URL contains the word clone.
• The Ephemeral environment is the temporary production environment. In Pega Cloud services, the URL contains the word ephemeral.

Note: This information is detected automatically in Pega Cloud environments, however we recommend you validate the environment URLs for each stage.

Environments

1. Deployment Manager pre-populates an update pipeline with six stages:
   • Staging-clone - Updated environment where the team validates their applications. Use this stage to fix any update impacts and source changes.
   • Ephemeral - This stage represents a short-lived environment that comes to life during the Go-no-Go phase. Update and deploy this environment with your production rule schema and data schema. Run confidence tests on this environment before you confirm updates on production.
   • Production - Actual production environment of the client. In a basic update, production updates after you approve the Go decision.
   • Staging - Actual staging environment of the client. In a basic update, staging updates after the production update completes.
   • Quality Assurance - Actual quality assurance environment of the client. In a basic update, staging updates after the production update completes.
   • Development - Actual development environment of the client. In a basic update, staging updates after the production update completes.
2. In the Authentication Profile field for the system, press the Down arrow key, and then select the authentication profile that you want to communicate from the orchestration server to the system.

Repositories

3. In the Artifact management section, select the development and production repositories through which the product rule that contains application moves through the pipeline.
4. In the Development repository field, select the development repository.
5. In the Production repository field, select the production repository.
6. Click Next.