Deployment Manager 5.1.1
Deployment Manager 5.1.1 includes the following new features and enhancements.
The following new features are available in this release:
- Flexible pipeline configurations now allow for customization of your pipeline model. Pipelines now support more than four stages, along with the ability to rename stages and add or remove tasks as required.
- Multispeed deployments provide the ability to queue multiple deployments in the same stage of a pipeline. With this functionality, developers can regularly merge their changes for to selective testing and promotion of deployments without blocking the pipeline. This approach introduces the concept of transition between stages that require user input to proceed.
- Pipeline templates have been added to define recommended release processes.
Deployment Manager supports the following
application pipeline templates:
- Business Change
- Business change pipelines support everyday, business-as-usual changes to
your application. With this new pipeline type, users can respond to changing
requirements by modifying and deploying application rules in a controlled
manner. For more information, see Managing the business-as-usual
Note: The business change pipeline feature in version Deployment Manager 5.1 is supported with customers on Pega Platform 8.5.2 or later. Customers are not recommended to upgrade to Deployment Manager 4.8.4, as the suggested upgrade path from Deployment Manager 4.8.3 is to 5.1. Candidate environments must be on Pega Platform 8.5.2 to use the business change pipeline feature.
- Environment templates are now utilized when creating or editing a pipeline. This feature automatically populates pipeline stages with associated tasks and determines what validations to apply. If you do not want to use an environment template, you can select a custom template to use all available tasks.
- Change sets are a new resource type used to track rule changes that are incorporated into a branch, which is further passed on to a deployment. With this functionality, users can trace the source of a deployment and associated work items.
- OAuth 2.0 is now used as the standard way to authenticate interactions. Deployment Manager supports candidates on basic authentication, but OAuth 2.0 authentication is recommended for secure two-way communication in candidate systems.
- Single Sign-On (SSO) is now supported. You can now follow the guided approach to configure SSO and an LDAP system integration. See Configuring SSO and LDAP for more information.
- As of Deployment Manager 5.1 and later, the existing cicd/v1 REST APIs have been deprecated and replaced with additional API support. For more information about the update, see the Swagger documentation.
The following enhancements have been implemented to existing Deployment Manager functionality:
- A new environments tab has been added to the pipeline creation screen, which stores the environment URL and authentication profile information. This tab is only visible during pipeline creation. You can modify this information after creating the pipeline by clicking directly on the appropriate stage.
- The task selection and configuration experience has been updated. When you add a task to a stage, a right-pane overlay is displayed so that you can enter required information.
- A single pipeline no longer supports both pre-merge criteria and deployment stages. As of Deployment Manager 5.1 and later, this criteria is represented by two separate pipelines, a merge pipeline and a deployment pipeline.
- A complete list of available tasks in Deployment Manager is now available in the task catalog. For more information, see Task catalog.
Dependencies and issues
Deployment Manager 5.1.1 is released with the following dependencies and known issues:
- Deployment Manager orchestrator system is supported only on Pega Platform version 8.5.2 or later.
- Pega Platform version 8.5.2 has a known issue with Nexus 2 and Nexus 3 repositories that results in an error only when you run diagnostics. That issue has no impact on the run-time execution of a pipeline with these repositories.
- Deployment Manager version 5.1.1 does not support custom tasks or integration with App Studio publishing. Later versions of Deployment Manager will re-introduce these features.
- If the default email account in the orchestrator is not configured or if the email ID is not configured for the operator, an exception stack trace is printed 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 version 5.1.1 does not support the option to skip a failed task.
- Jenkins integrations now require OAuth 2.0 to be enabled.
- Diagnostics fail to identify the ability of the candidate environment to access the orchestrator. This currently impacts the execution of data migration pipelines. Ensure that your candidate can access the orchestrator by following the steps outlined in Setting up candidate environments.
- Deployment Manager 5.1 does not currently support the ability to trigger a deployment using an existing artifact.
Previous topic Deployment Manager 5.2.1 Next topic Deployment Manager 4.8.4