Skip to main content
Matrix42 Self-Service Help Center

Deployment Management

Overview

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. 

HOME PAGE

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.

clipboard_eef189a81d4c80125577df93a98b22141.png

Deployment Plan

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:

Deployment_management_deployment_plan.png

Products

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:

Deployment_management_products.png

Configure Deployment

Action "Configure Deployment" automatically prepares the product for the standard deployment of Configuration Packages.

The system automatically creates Configuration Project, Pipelines, etc. 

Deployment_anagement_configure_deployment_action.png

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.

Features

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:

Deployment_management_features.png

Source Control

Repository structure

clipboard_e4bc3034d16512ddb48b60933fbc89766.png

Editing Files

clipboard_e0b7fe0be6745d90ffebd856dd7e6ef08.png

Reviewing commits

clipboard_ec02e9f3b9b4ca67a537d99ee35b9979f.png

Review Commit details

clipboard_ecbf928d1902339657c38e54264d34eed.png

 

Adding files

clipboard_e51ccc9627167186f8b4c891bda0ff5d2.png

Pipelines

Deployment Management integrates with Microsoft Azure DevOps that provides complete tool chain to manage, automate and deploy your build very easily and effectively.

Build Pipelines

They are part of the Build Process that deals with building releases and ensures all components are ready to enter the testing phase.

clipboard_e50ea98296942ef024f2716f631ad70cd.png

Deployment Pipelines

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.

clipboard_e49832de1c3c85e15f0b5beef17f08db9.png

Also, alternatively, Retire pipeline, uninstalls release from the environments

Environments

List of environments in every project that can be used for Deployments

clipboard_e9f9cb7b9b2e05744acd895d60b0cba43.png

Changes

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.

Deployment_management_changes.png

Environments

 

Configuration

Product Capability

It is possible to review and update products with selected capability

clipboard_e82c3b8adef3dd0084dea4e9cdbf7c188.png

 

Settings

Application settings

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

clipboard_ef56053ff9b65c7a5ebdf1145358bd64a.png

Integration

In order to configure the integration with Azure DevOps, every user needs to have the Organization name and token configured in User Profile

clipboard_e3e97045f290ad4a08cc82758d7b8049b.png

 

  • Was this article helpful?