Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Running post-upgrade steps

Updated on February 4, 2021

If you are upgrading from Deployment Manager versions earlier than 3.2.1, you must run post-upgrade steps to complete the upgrade. Before you run post-upgrade steps, ensure that no deployments are running, have errors, or are paused. In Pega Cloud Services environments, the orchestration server name is similar to [environmentname]-DevOps.

If you are upgrading from Deployment Manager 3.2.1 or later, skip this section; otherwise, do the following steps:
  1. On each candidate system, update the PegaDevOpsFoundation application version to the version of Deployment Manager that you are using.
    1. In the header of Dev Studio,, click the name of your application, and then click Definition.
    2. In the Built on application section for the PegaDevOpsFoundation application, in the Version field, press the Down arrow key and select the version of Deployment Manager that you are using.
    3. Click Save.
  2. Modify the current release management application so that it is built on PegaDeploymentManager:4.7.x:
    1. In the header of Dev Studio, click the name of your application, and then click Definition.
    2. In the Edit Application rule form, on the Definition tab, in the Built on application section, for the PegaDeploymentManager application, press the Down arrow key and select 4.6.
    3. Click Save.
  3. If you do not see the pipelines that you created in earlier releases, run the pxMigrateOldPipelinesTo42 activity:
    1. In the header of Dev Studio, search for pxMigrateOldPipelinesTo42, and then click the activity in the dialog box that displays the results.
    2. Click ActionsRun.
    3. In the dialog box that is displayed, click Run.
  4. On the orchestration server, run the pxUpdateDescription activity.
    1. In the header of Dev Studio search for pxUpdateDescription, and then click the activity in the dialog box that displays the results.
    2. Click ActionsRun.
    3. In the dialog box that is displayed, click Run.
  5. On the orchestration server, run the pxUpdatePipeline activity.
    1. In the header of Dev Studio, search for pxUpdatePipeline, and then click the activity in the dialog box that displays the results.
    2. Click ActionsRun.
    3. In the dialog box that is displayed, click Run.
  6. Merge rulesets to the PipelineData ruleset.
    1. Click ConfigureSystemRefactorRulesets.
    2. Click Copy/Merge RuleSet.
    3. Click the Merge Source RuleSet(s) to Target RuleSet radio button.
    4. Click the RuleSet Versions radio button.
    5. In the Available Source Ruleset(s) section, select the first open ruleset version that appears in the list, and then click the Move icon.
      Result: All your current pipelines are stored in the first open ruleset.
  7. If you modified this ruleset after you created the application, select all the ruleset versions that contain pipeline data.
    1. In the target RuleSet/Information section, in the Name field, press the Down arrow key and select Pipeline Data.
    2. In the Version field, enter 01-01-01.
    3. For the Delete Source RuleSet(s) upon completion of merge? option, click No.
    4. Click Next.
    5. Click Merge to merge your pipelines to the PipelineData:01-01-01 ruleset.
    6. Click Done.
Result: Your pipelines are migrated to the Pega Deployment Manager application.
What to do next: Log out of the orchestration server and log back in to it with the DMReleaseAdmin operator ID and the password that you specified for it.
Note: You do not need to perform any of the required steps in the remainder of this document. If you want to use Jenkins tasks to configure email notifications, see Configuring Jenkins.

Tags

Pega Platform 8.5 DevOps

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us