LinkedIn
Copied!

Table of Contents

Deployment Manager 5.3.1

Deployment Manager 5.3.1 includes the following new features.

Enhancements

This release contains the following new features:

  • Deployment Manager now supports upgrade pipelines, a new pipeline template that you use to automate and simplify near-zero-downtime upgrades in order to promote the latest application features to your production environment. When you use Deployment Manager as a standard DevOps approach during upgrades, you can assess the effect of the latest Pega Platform features and plan your new feature adoption strategy across your environments after you upgrade to the latest version of Pega Infinity. To get started with upgrade pipelines, see Creating an upgrade pipeline.
  • The Deploy task includes a new parameter, which allows Deployment Manager to manage aged updates for a stage. You can now configure the task details to override, skip, or ignore aged updates as a default action. For more information, see Managing aged updates.
  • In addition to the abort and retry options, you can now skip failed tasks in a deployment. After you skip a task, the deployment continues to the next task in the pipeline. For more information, see Managing a deployment that has errors.
  • Deployment Manager now enables custom tasks to configure any integration capabilities that has external systems on the orchestrator. For more information, see Creating and using custom tasks.
  • Deployment Manager now supports data migration pipelines. Any pipelines from previous versions of Deployment Manager require migrating the pipeline or creation of a new pipeline. For more information, see Migrating data to Deployment Manager 5.

Dependencies and issues

Deployment Manager 5.3.1 contains the following dependencies and known issues:

  • Pega Platform version 8.5.2 has a known issue with Nexus 2 and Nexus 3 repositories,which results in an error when you run diagnostics. This issue has no impact on the run-time execution of a pipeline with these repositories.
  • If the default email account in the orchestrator is not configured or if the email ID is not configured for user, Deployment Manager prints an exception stack trace in the logs. To avoid this issue, turn off the logging level for com.pega.platform.integrationengine.client.email.PegaEmailClient and com.pegarules.generated.pega_integrationengine_default.
  • Deployment Manager consumes the latest application version unless you specify otherwise.
  • The enterprise application defined in a business change pipeline cannot increment a minor version later than v99. You must manually roll over your versioning if your application or ruleset versions encounter this scenario.
  • If you upgrade from Deployment Manager 4.x or 5.1 to 5.3, you must recreate business change pipelines due to an internal property configuration. If you upgrade from Deployment Manager 5.2, you can reuse the existing pipeline.

Resolved issues

Deployment Manager 5.3.1 contains the following software fixes:

  • Auto-refresh now works as expected from within Deployment Manager, it no longer requires a reload of the UI.
  • Deployment Manager now properly fetches privileges if the role name contains punctuation, such as a colon or semicolon.
  • ResumeNextQueuedDeployment no longer runs automatically and checks for a deployment ID before it executes, which resolves an issues that cause an infinite loop if no deployment was queued.
  • Complete artifact history now functions when you merge multiple branches and generate a new artifact.
  • When you use the Nexus repository, you can now download artifacts in merge pipelines.
  • An issue with Deployment Manager that displays the "Unable to attach log files" error when you execute or update a task has been resolved.
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.