Table of Contents

Configuring upgrade pipelines in Deployment Manager versions 4.8.2 to 4.8.4


Only available versions of this content are shown in the dropdown

Create an upgrade pipeline for each application that you need to upgrade. This pipeline promotes any upgrade fixes and testing assets for confidence testing.

Note the following information about your environments in Deployment Manager:

  • The Development stage is the upgraded, cloned, staging environment where you make upgrade fixes. On Pega Cloud Services, its URL contains “clone”.
  • You can ignore the Quality Assurance stage in upgrade pipelines.
  • The Staging stage is the temporary, cloned production environment. On Pega Cloud Services, its URL contains “ephemeral”.
  • The Production stage is the production environment. On Pega Cloud Services, its URLs contains “prd".

See the following figure for an example:

Deployment Manager environments

For Pega Cloud Services upgrades, you can view the upgraded, cloned, staging environment and the temporary, cloned production environment in the My Pega Cloud portal. For more information on managing upgrades in the My Pega Cloud portal, see Upgrades.

If you cannot access your DevOps environment, request support from Pegasystems Global Client Support by selecting New request in My Support Portal. For the latest documentation on making requests, see My Support Portal: New Design, Streamlined Features.

When configuring an upgrade pipeline, you must do the following tasks:

  • Add the following two product rules to the Staging stage that are required to perform go/no-go confidence testing:
    • The application product rule, which includes any fixes that you made to support the upgrade. You must also select the access group to which the application belongs by pressing the Down arrow key in the Access group field when you configure a pipeline in Deployment Manager.
    • The confidence test case product rule, which contains all the data instances, such as the access groups and operator IDs.

    See the following image for these product rule fields:

    Configuring rules to be promoted during the Staging stage
  • On the pipeline model, clear the check boxes to disable the Staging and Production stages. Enable these stages later when you are ready to begin the deployment and promote your upgrade fixes and confidence testing assets.
  • In the Production stage, add a manual task before the Deploy task to represent the outcome of the go/no-go decision. Accept this task to promote upgrade fixes to your production environment. This stage should include your application product rule, but not your confidence test case product rule. See the following figure for reference:
    Pipeline stages in Deployment Manager
  • Configure your pipeline to merge branches and perform tasks, such as running PegaUnit tests, on your Development stage (cloned staging environment). You can also configure other settings, for example, you can specify Jenkins server information if you are using Jenkins to run regression tests.

Have a question? Get answers now.

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