Table of Contents

Understanding upgrade pipelines

Keeping current enables your application to utilize the latest features, performance improvements, and security fixes to maximize customer success. Enhancing your Pega solution is now a simple and convenient process.

The basic upgrade phase upgrades Pega Infinity rules to the latest version with minimum disruption. This phase takes you about two weeks to complete and performs any necessary application changes to ensure functional correctness and upgrade compliance. You can adopt the latest performance and security improvements and test existing functionality using your current testing processes. This phase excludes adopting features of the new version of Pega Infinity to ensure a near-zero-downtime upgrade of the production environment.

Deployment Manager plays a crucial role in the basic upgrade phase of the process. Upgrade pipelines automate and simplify the near-zero-downtime upgrades to minimize the risk of upgrade failures.

Deployment Manager in the upgrade process
Using Deployment Manager to automate and simplify the upgrade process

Upgrade pipelines are only available in Deployment Manager 5.3 or later and it is recommended that you request an upgrade for the Deployment Manager orchestrator during the validation phase of the basic upgrade process.

Managing upgrade fixes

Deployment Manager ships the KeepPegaCurrent application responsible for managing the upgrade fixes identified during the validation phase in the basic upgrade process.

The KeepPegaCurrent application has two product rules:

  • UpgradeFixes
    • You must package your upgrade fixes across multiple applications in the upgradeFixes product rule. For each application this impacts, you must lock and roll a new ruleset version.
  • UpgradeTestAsset
    • You must package the test assets you require to test during the go-no-go process in the UpgradeTestAssets product rule.

Managing operators in the upgrade process

Upgrade pipelines require you to assign certain access roles and privileges before proceeding.

To create an upgrade pipeline, ensure you have the proper access role and privileges. Only operators with app admin and superadmin roles can create upgrade pipelines. If an application administrator wants to create an upgrade pipeline, they must have access to the KeepPegaCurrent application. This application is used to deploy upgrade fixes through the pipeline. Upgrade pipelines also require the appointment of a Go-no-Go approver at the time of pipeline creation. The Go-no-Go approver represents the stakeholder responsible for approval tasks in the pipeline.

Go-no-Go approvers must have an operator in Deployment Manager with access to the KeepingPegaCurrent application and the approve/reject privilege. See Assigning privileges for more information.

Managing the upgrade process

During a basic upgrade process, you create an upgrade request on My Pega Support Portal for Pega Cloud. To receive this request, Pega provides a cloned and upgraded staging environment to validate the impact of the upgrade on client applications.

We recommend that you upgrade the Deployment Manager environment to leverage upgrade pipelines to manage upgrade fixes through the upgrade process.

If you are on Pega Cloud Services, an upgraded Deployment Manager instance enables you to create upgrade pipelines to detect your environments. On-premise and client cloud customers can leverage upgrade pipelines by filling in the environment details and managing the product rule.

Upgrade pipelines are valuable during the validation phase to help with compliance guardrails.

When you are ready to sign off on the validation and begin the upgrade process, do the following:

  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 Start deployment on the upgrade pipeline to begin the upgrade process.

  3. After the Staging-Clone stage completes, the upgrade queues for promotion.

  4. Notify Pega that you are ready to proceed with your software upgrade by indicating that UAT is complete. See Pega Cloud Services upgrade checklist for Pega Infinity release 8.4.2 and later for more information.

  5. From Deployment Manager, promote the upgrade to the Ephemeral stage.

  6. Ensure you secure the Ephemeral stage (temporary production URL) details from My Pega Cloud.

  7. Log in to your temporary production URL and update the DMReleaseAdmin_oAuth2 profile and the DMAppAdmin operator passwords. This allows you to interact with Deployment Manager and complete the Go-no-Go confidence testing. This may require you to recreate the profile and operator.

  8. After the previous step completes, approve the Enable DMAppAdmin task on the upgrade.

  9. The upgrade is now waiting for the Go-decision approval. Perform the confidence tests after eabling the operators required for the testing. You can package the operators in the upgradeTestAssets product rule and deploy to the Ephemeral stage with no additional configuration.

  10. To continue with the production upgrade, you must indicate approval for the upgrade on production by clicking the Action center banner in the My Pega Cloud portal and provide the relevant information.

  11. After the rolling upgrade of the production environment is complete, approve the Confirm upgrade readiness task for deploying upgrade fixes

  12. For non-production upgrades:

    1. If the upgrade is pending promotion to the non-production stages, you must manually promote the upgrade to the next stage.
    2. The upgrade waits for the approval of the Confirm upgrade readiness task. Once you upgrade the staging environment, you can approve the task.
    3. The upgrade moves to the Quality Assuance stage and waits for approval for Confirm upgrade readiness task. Once you upgrade the Quality Assurance stage, the task must be approved for the upgrade fixes to deploy.
    4. The above steps must be repeated for the Development stage.
    Diagnostics will fail on upgrade pipielines due to the generation method of upgrade pipelines for Pega Cloud clients. Deployment Manager retuns an error when connecting to the ephemeral node on Pega Cloud since the ephemeral environment is temporary and only during Go-no-Go phase.
Did you find this content helpful?

Have a question? Get answers now.

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