Resources

Connecting Azure DevOps to WayFinder to include source control and CICD pipeline data

In order to get Lead Time, Deployment Frequency and Change Failure Rate metrics, you need to add source control and CICD Pipeline data sources for your product in WayFinder.

Connecting your Azure DevOps repositories and pipelines can provide this data. There are three items you will need:

• Azure DevOps organisation identifier
• Azure DevOps Personal Access Token (PAT)
• CICD pipeline production deployment stage names

Your user may be part of multiple Azure DevOps organisations. You will need the identifier for the organisation that contains the repositories and pipelines you want to include in WayFinder.

Least Privilege and Least Data

We aim to ingest only the minimum data possible to provide you with metrics. For Azure DevOps you remain in control of this by providing WayFinder with a Personal Access Token.

If you have previously created an Azure DevOps PAT for WayFinder you can skip this section and reuse the token you previously created. If you no longer have a copy of that token, just create a new one but do not delete or regenerate the previous token or the other data source will stop working.

Creating a PAT

Follow the instructions from Azure DevOps to Create a PAT.

What permissions are needed?

We aim to use least privilege and therefore only the following permissions are needed to be added to the PAT:

• Code:Read

In WayFinder we have a grouping called a “Product”. When organisations are developing a product or service there are typically multiple repositories and multiple CICD pipelines.

For example there may be a frontend repository and a backend repository and each may have it’s own CICD pipeline for deployment. The metrics for the "Product" are aggregated to include all the associated repositories and their CICD pipelines.