Cloud Services

DevOps Intelligence

Expand menu Collapse menu

Azure Release Pipelines configuration

Published On Dec 12, 2024 - 1:59 PM

Azure Release Pipelines configuration

Learn how to configure DevOps Intelligence for the integration of Azure Release Pipelines to broaden the observability of your hybrid IT estate.

To enable effective data synchronization from Azure Release Pipelines into DevOps Intelligence, it's crucial to establish an adequately configured Azure DevOps connection. This connection is a secure bridge between the two platforms, allowing seamless data transfer and management. Establishing this connection enables DevOps Intelligence to leverage Azure Pipeline's robust capabilities, enhancing its monitoring and reporting features. This configuration enhances the accuracy and efficiency of data handling and amplifies the overall functionality of the DevOps Intelligence tool.

Access rights
: The connection must have the following access rights:

Build and Deploy
: Read access right.

User profile
: Read access right.

To access templates, you must have specific roles; please see:

Roles required

As a user, your permissions determine the actions you can perform on the bring-your-own (BYO) template data. You must view, create, update, and delete roles to perform the respective actions. By default, these permissions are granted to the Editor. The Viewer, on the other hand, is only endowed with the view role.

Configuring Azure Release Pipelines for recent customers

The procedures in this section are valid only for customers onboarded 6 June 2024 or after. Procedures for legacy customers are provided in the subsequent section Configuring Azure Release Pipelines for DevOps Intelligence, legacy customers
.

Use the following procedure to configure the DevOps Intelligence for Azure Pipelines:

Tools must be configured for a specific application in a specific DevOps phase. In step 2 of the following procedure, you are choosing the application and DevOps phase to associate with Azure Release Pipelines as part of the configuration procedure.

Click
Settings & Utilities
→ Application Configuration
. You will see a list of existing applications.

Select the existing application for which you want to configure Azure Release Pipeline or create a new application.

Click the overflow menu (vertical ellipsis) on the Deploy row for the selected application.

Select Add New Tool Configuration
from the overflow menu. The service displays the Add Tool Configuration form.

Select Azure Release Pipelines for Tool Engine
.

Click Submit
.

Onboarding Azure Release Pipelines

After configuring Azure Release Pipeline, you must onboard the technical service. Use the following procedure:

Click the overflow menu for the selected application.

Select Onboard Technical Service
. The service displays the Onboard Technical Service form.

Select Deploy
for DevOps Phase
. The service displays the Tool Engine field.

Select Azure Release Pipelines
for Tool Engine
. The service displays the Connection
field.

Select the appropriate connection. The service displays the Select Organization
field.

Select the appropriate organization. The service displays the Select Projects
field.

Select the appropriate project. The service displays the Repository Name
field.

Select the appropriate repository.

Click Onboard
. The service navigates to the Application Configuration page.

You now have the option of clicking the overflow menu for Develop and selecting Edit/Delete Tools Configuration
to confirm that Azure Repo has been fully configured.

Deleting Azure Pipelines as a technical service

The administrator may, at will, delete the Azure Pipeline technical service. Use the following procedure:

Navigate to DevOps Intelligence → Settings & Utilities
→ Application Configuration
.

Expand the application to view all associated phases.

Click the Overflow menu for Deploy
.

Click Delete Technical Service
.

Click Azure Pipelines for Select Tools Configured
. The service displays the Select Organization
field.

Select the appropriate organization. The service displays the Select Projects
field.

Select the appropriate project.

Click Delete
.

Configuring Azure Release Pipelines for DevOps Intelligence, legacy customers

You must choose the Pipeline name, add a Technical Service and additional configurations for customizations to establish the configuration. Extra settings are available to handle the states of Passed
, Failed
, and In Progress
, which are terms employed in the DevOps Intelligence dashboards. You have the flexibility to introduce custom terms for these states. For instance, any value input under the "Passed" category will be interpreted as "Passed" when displayed on the dashboard. Once you have made these selections complete the following steps to configure AWS CodePipeline:

Within Kyndryl application, select the Open menu icon from the top left corner, navigate to DevOps Intelligence
and expand the menu.

Expand Settings & Utilities,

then select Tools Configuration.

Select Add configuration +
and a Add tool configuration
form will be displayed; here, you will select:

Azure Pipeline - Build
from the Tool Engine
dropdown menu.

The Connection
, Test type
, Technical service
, Organization
and Project
each one from its dropdown menu.

And you can fill in the
Additional configuration for customization
section at the bottom of the form if you would like to personalize it with custom terms for Passed
, Failed
or In progress
statuses.

Select the Add configuration
button at the bottom of the form.

After completing the configuration, you can view the configuration details in the table on the configuration page. A sample image showcasing this is provided below for your reference.

Build

Deploy

Do you have two minutes for a quick survey?

Take Survey