Skip to main content

Migrating update fixes to production

Suggest edit
Updated on April 12, 2022

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

Repeat the following procedure for each update pipeline:
  1. If the pipeline is not open, in the navigation pane of Deployment Manager, click Pipelines and then click the name of the pipeline.
  2. Click ActionsPipeline model.
  3. At the top of the page, click the back icon.
  4. Diagnose your pipeline to troubleshoot issues and verify your pipeline configuration. For more information, see Diagnosing a pipeline in 5.3.x.
  5. Perform the following steps:
    1. In the Description field, enter descriptive text about the deployment.
    2. Click Submit.
    Result: 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-NoGo decision.
  6. For each application, perform application confidence testing on the temporary production environment. For more information, see Understanding confidence testing.
  7. If you are updating on Pega Cloud services, go to My Pega Cloud and indicate your approval for the update on your production environment. You can skip this step if you update from an earlier version or for on-premises systems.
    1. In the My Pega Cloud portal, on the Home page, click the Action center banner.
    2. On the Updates stage screen, click Go-NoGo.
    3. In the Go-NoGo decision dialog box, select the checkboxes for each task to indicate that you have completed them.
    4. From the Go-NoGo Approval list, select Go to proceed with the update or NoGo to abandon the update.
    5. To proceed with the update and initiate the rolling restart, select the Continue with immediate rolling update checkbox.
    6. Click Submit.

      For more information on managing updates in the My Pega Cloud portal, see Upgrades.

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

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

  8. Complete the manual approval step that represents the outcome of the Go-NoGo decision to move the application and test packages to production.
    Complete the manual step from within an emailClick Accept.

    For more information, see Configuring Deployment Manager notifications.

    Complete the manual step in the pipeline
    1. If the pipeline is not open, in the navigation pane, click PipelinesApplication pipelines, and then click the name of the pipeline.
    2. Click Complete.
What to do next: Approving the manual step resumes the deployment to the production environment, which reimports any data instances in the application product using the application test product rule you created earlier in your update pipeline.
  • Previous topic Syncing rules between the production environment and the updated, cloned, staging environment in Deployment Manager
  • Next topic Understanding confidence testing
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us