Deployment Manager 4.6.1
Deployment Manager 4.6.1 includes the following enhancements and resolved issues.
The following enhancements are available in this release:
- Ability to use Deployment Manager to automate data migration pipelinesData migration pipelines allow you export data from a production environment to a simulation environment where you can test impact of the changes made to your decision framework safely without having to deploy to a production environment. You can now use Deployment Manager to create data migration pipelines that allow you to automatically export data from a production environment and import it into a simulation environment. Additionally, you can configure a job scheduler rule to run pipelines during a specified period of time.For a tutorial on configuring simulation pipelines, including how to use Deployment Manager with them, see Deploying sample production data to a simulation environment for testing.For more information about configuring and using simulation pipelines with Deployment Manager, see Data migration pipelines with Deployment Manager 4.6.x.
- Ability to provide access to Dev Studio to a roleYou can now allow a role to access Dev Studio, and all the users of that role can switch to Dev Studio from the Operator icon. By being able to switch to Dev Studio, users can access Dev Studio tools to further troubleshoot issues that Deployment Manager cannot diagnose.
- Ability to easily move to new orchestration systems by configuring a dynamic system settingWhen you move from an existing orchestration system to a new one, you can now configure a dynamic system setting that specifies the URL of the new orchestration system.
Resolved issues in Deployment Manager 4.6.1
The following issues were resolved in this release:
The position of the Validate test coverage task was not retained.
If you added a Validate test coverage task in a pipeline, the task automatically moved under the Add task menu option after you saved the pipeline configuration. The position of the task is now saved.
Deployment Manager installation failed on IBM Db2.
Deployment Manager installations on systems running on Db2 failed with a database error. You can now install Deployment Manager on Db2.
Not all API requests included PRRestService.
Some HTTP requests to the api service package did not include PRRestService. It is now included in all requests if it is needed to direct all traffic to the API node.
Tasks could not be added before the Deploy task in Deployment Manager 4.5.1 when using the API.
When you used the API to create pipelines, you could not add tasks before the Deploy task, although you could add a task when you configured the pipeline in Deployment Manager. You can now add tasks before the Deploy task with the API.
Test changes in branches were merged into incorrect ruleset versions.
Sometimes, test changes in branches were merged into an incorrect ruleset version if multiple application versions were used and a test application was configured on the pipeline. Test changes in branches are now merged into the correct ruleset versions.
Deployment Manager displayed a message for reaching the limit for pending changes.
Sometimes, Deployment Manager displayed an error message that you reached the maximum limit for pending changes. The limit has been increased, and the error no longer appears.
The Jenkins configuration diagnostics check failed when cross-site request forgery (CSRF) protection was disabled.
When CSRF protection was disabled in Jenkins, pipeline diagnostics for Jenkins configuration failed with an error message that the Jenkins server was not reachable, even though the Jenkins task in the pipeline worked correctly. Jenkins diagnostics checks no longer fail in this scenario.
Previous topic Deployment Manager 4.7.1 Next topic Deployment Manager 4.5.1