Azure Pipelines configuration

learn how to configure for the integration of azure pipelines to broaden the observability of your hybrid it estate to enable effective data synchronization from azure pipelines build into , 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 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 tool access rights the connection must have the following access right build read access right user profile read access right 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 for azure pipelines recent customers note 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 for azure pipelines, legacy customers use the following procedure to configure the for azure pipelines note 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 pipeline 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 pipelines or create a new application click the overflow menu (vertical ellipsis) on the build row for the selected application select add new tool configuration from the overflow menu the service displays the add tool configuration form select build for build categories the service displays the tool engine field select azure pipelines for tool engine the service displays the status field enter the current statuses of the builds of the azure pipelines (passed, failed and in progress, multiselect) click submit onboarding azure pipelines after configuring azure 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 build for devops phase the service displays the tool engine field select azure pipelines for tool engine the service displays the select 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 pipelines 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 → settings & utilities → application configuration expand the application to view all associated phases click the overflow menu for build 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 for azure pipelines, legacy customers note the procedures in this section are valid only for customers onboarded before 6 june 2024 you must choose the project and organization and 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 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 overflow menu button from the top left corner, navigate to 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