Migrating upgrade fixes to production

When you are ready to migrate your upgrade fixes, deploy your changes first to the ephemeral stage and then to production. Promoting your application and upgrading to production ensures that your application is updated with the latest features and capabilities after an upgrade. On Pega Cloud Services, you perform these steps after entering your 60-minute validation window.

You enable your staging and production stages and start a deployment to the production environment.

Repeat the following procedure for each upgrade pipeline:

1. If the pipeline is not open, in the navigation pane of Deployment Manager, click Pipelines Application pipelines , and then click the name of the pipeline.

2. Click Actions Pipeline model .

3. If you use Deployment Manager version 4.8.2 to 4.8.4, select the check boxes for the Staging and Production stages to enable them, and then click Save.

4. At the top of the page, click the back icon.

5. Diagnose your pipeline to troubleshoot issues and verify your pipeline configuration. For more information, see one of the following topics:

   • For Deployment Manager version 4.8.2 to 4.8.4, see Diagnosing a pipeline.
   • For Deployment Manager version 5.1 or later, see Diagnosing a pipeline in 5.1.x.

6. If you use Deployment Manager version 4.8.2 to 4.8.4, start a deploy perform the following steps:

   1. In the Start deployment dialog box, click Start deployment.

   2. Click Generate new artifact.

   3. In the Deployment name field, enter descriptive text about the deployment.

   4. Click Submit.

      When you run the deployment, and Deployment Manager promotes your changes to the temporary production (ephemeral) environment. The deployment stops at the manual task in the Production stage that you added to indicate the go/no-go decision.

7. If you use Deployment Manager version 5.1 or later, perform the following steps:

   1. In the Description field, enter descriptive text about the deployment.

   2. Click Submit.

   When you run the deployment, and Deployment Manager promotes your changes to the temporary production (ephemeral) environment. The deployment stops at the manual task in the Production stage that you added to indicate the go/no-go decision.

8. For each application, perform application confidence testing on the temporary production environment. For more information, see Understanding confidence testing.

9. If you are upgrading on Pega Cloud Services, go to My Support Portal and, in the My Pega Cloud tab, indicate your approval for the upgrade on your production environment by using the go/no-go banner. You can skip this step if you upgrade from an earlier version or for on-premises systems.

   In Pega Cloud environments, Pega deletes the temporary production URL and initiates a rolling restart of your live (production) environment.

   If you make a no-go decision, the upgrade does not proceed, an operations engineer contacts the you for information about why the upgrade was stopped, and then the engineer reschedules the upgrade.

10. Complete the manual approval step that represents the outcome of the go/no-go decision to move the application and test packages to production.

    Choice	Actions
    Complete the manual step from within an email	Click Accept. For more information about email notifications, in Deployment Manager version 4.8.2 to 4.8.4, see the following topics: Configuring email accounts on the orchestration server Understanding Deployment Manager notifications For more information about email notifications in Deployment Manager version 5.1 and later, see the following topics: Configuring email accounts on the orchestration server Understanding Deployment Manager notifications
    Complete the manual step in the pipeline	If the pipeline is not open, in the navigation pane, click Pipelines Application pipelines , and then click the name of the pipeline. Click Complete.