Deployment Management aims to ensure that your releases are deployed into production efficiently and effectively. Deployment management works closely with release management and change management but is a separate practice. In some organizations, the term ‘provisioning’ is used to describe the deployment of infrastructure, and deployment is only used to mean software deployment, but in this case the term deployment is used to mean both.
This functionality will be made available soon as a package on our Matrix42 Extension Gallery.
The Home page provides a bird's-eye view of the key information about the Deployment Success Rate, Deployment Frequency, and Deployment Issues according to the selected Product.
The Deployment Plan outlines the scope, approach, and execution planned for the deployment of the project deliverables. The plan includes, where relevant, information about system support, issue tracking, escalation processes, roles and responsibilities before, during, and after deployment. The deployment plan is intended to provide clients, stakeholders, and support personnel with a smooth transition to the new product or software being deployed.
The deployment plan describes each step of the deployment process at each deployment location, whether there is one site or multiple sites, or one deployment or a phased deployment planned. The Deployment Plan defines all of the work steps for complete deployment, and who does them:
Use the Products section to manage a list of products: create and describe its purpose, assign Responsible Team, Product Owner, and set Deployment Type(s).
Add Releases so that they are transformed in a Roadmap on the Product preview:
Action "Configure Deployment" automatically prepares the product for the standard deployment of Configuration Packages.
The system automatically creates Configuration Project, Pipelines, etc.
Deploy and Retire the product
With the Deployment Management extension, it is possible to trigger Deployment or Retire the product from the selected environments.
This requires the Deployment and Retire pipeline to be configured first.
In addition, deployment and retirement can be triggered automatically according to configured schedule in Administration → Engine Activations.
Every Feature is a part of a defined Product and is delivered in a specified Release. It has a Priority, Status, Planned Start and End Dates, and can be assigned to a team. Additionally, you can add Tasks that are related to this feature or report Tickets or Problems that occurred due to this feature:
Review Commit details
Deployment Management integrates with Microsoft Azure DevOps that provides complete tool chain to manage, automate and deploy your build very easily and effectively.
They are part of the Build Process that deals with building releases and ensures all components are ready to enter the testing phase.
The objective of the Deployment Pipeline is to deploy new releases in the live environment and also arrange training for end-users and operating staff.
Also, alternatively, Retire pipeline, uninstalls release from the environments
List of environments in every project that can be used for Deployments
Changes are generally used for automated phases of the release lifecycle.
For instance, when using "Default Release Template " the Phase "Release Testing" is linked to the "Release Management - Testing Release Phase" Change template.
When Release status is changed to "Ready for Testing" the system will create a new Change and start the process of validation automatically.
A new Change will have a list of tasks. The actor needs to Close the task that is related to change that is related to release as Directly solved -> Release will automatically change the status to Ready for Shipment. Otherwise close task as Rejected - Problem will be created
When the Validation state ends - release status will be changed to "Ready for Shipment" which will trigger the next phase - Deployment.
It is possible to review and update products with selected capability
Quality Threshold - a maximum allowed times for Deployment failures until Delivery Manager will be escalated
Delivery Manager - It is possible to configure Delivery Manager that will be escalated in case deployments fails max allow of times
Verification Template is used for validation of Deployments
In order to configure the integration with Azure DevOps, every user needs to have the Organization name and token configured in User Profile