Deployment Manager 4.5.1
Deployment Manager 4.5.1 includes the following enhancements and resolved issues.
The following enhancements are provided in this release:
- Ability to add tasks before Deploy and Publish tasksFor additional validation or environment provisioning, you can now add any task before the Deploy and Publish tasks, which are automatically added to the pipeline. You can add tasks before the Deploy task in any stage of the pipeline or before the Publish task in the development stage.
- Ability to associate bugs and user stories to branch mergesWhen you start a deployment by submitting a branch into the Merge Branches wizard, you can now associate user stories and bugs from Agile Workbench so that you can track branch merges.
- New REST API to deploy existing artifactsDeployment Manager now provides a REST API to deploy existing artifacts so that you can start a production pipeline with the output of the development pipeline for the same application. You can view the Documentation/readme-for-swagger.md file for more information on using the API.
- Ability to access and pass all relevant parameters of the current deployment for Jenkins tasksFor Jenkins tasks, you can now access and pass all the relevant Jenkins parameters for the current deployment, which include PipelineName, DeploymentID, RespositoryName, and ArtifactPath. When you configure the Jenkins task in a pipeline, the values of the parameters are automatically populated.
- More diagnostics to troubleshoot pipelinesYou can now automatically diagnose more issues with your pipeline so that you spend less time manually troubleshooting. For example, you can now verify that Jenkins steps are properly configured, and you can also obtain more information about repository connections with enhanced troubleshooting tips.
- Elimination of post-upgrade steps when upgrading from Deployment Manager versions 3.2.1 and laterFor upgrades from Deployment Manager 3.2.1 or later to version 4.5.1, you no longer need to run activities or do any other post-upgrade steps. After the upgrade completes, Deployment Manager performs health checks before running post-upgrade steps for both on-premises and Pega Cloud Services environments.
The following issue is resolved in Deployment Manager 4.5.1:
- Unable to configure keystores in Pega Cloud Services environmentsIf your target environment is SSL-enabled with private certificates, you can now set the keystore for Deployment Manager connectors so that they can receive and process tokens. You first configure a keystore and then update a dynamic system setting to reference the keystore ID. For more information, see "Step 3a: Configuring authentication profiles on the orchestration server and candidate systems" for your version of Installing, upgrading, and configuring Deployment Manager.
Previous topic Deployment Manager 4.6.1 Next topic Deployment Manager 4.4.2