Skip to main content

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

Upgrade Deployment Manager without running post-upgrade steps (8.3)

Updated on May 3, 2021

When you are upgrading to Deployment Manager 4.5.1 from 3.2.1 or later,  manual post-upgrade steps are no longer required for either on-premises or Pega Cloud Services environments. After Deployment Manager upgrades, a health check is run on your system; after it passes, post-upgrade steps run automatically.

By eliminating manual post-upgrade steps, you can quickly upgrade to new versions of Deployment Manager with ease. Additionally, on cloud, you can continue to use Deployment Manager without data loss while the post-upgrade steps complete.

Deployment Manager upgrade


For more information, see Understanding model-driven DevOps with Deployment Manager.

  • Previous topic Start a Deployment Manager deployment in a distributed, branch-based environment by using the Merge Branches wizard (8.3)
  • Next topic Track changes for branch merges in Deployment Manager (8.3)

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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