Skip to main content

Azure DevOps

CatalogScorecards

Summary

Azure DevOps is a Microsoft-owned VCS. You can use Azure DevOps to drive insights into values such as:

  • Repository details in the Catalog
  • Scorecard rules

Setup

In order to connect Cortex to your Azure DevOps instance, you’ll need to add a Azure DevOps personal access token with at least read scopes enabled.

caution

If you do not see the Settings page you're looking for in the sidebar, you likely don't have the proper permissions and need to contact your admin.

caution
If you're using a self-hosted instance of Azure DevOps, you'll need to verify that your Cortex instance is able to reach the Azure DevOps instance.
We route our requests through a static IP address. Reach out to support at help@cortex.io to receive details about our static IP. If you're unable to directly whitelist our static IP, you can route requests through a secondary proxy in your network that has this IP whitelisted, and have that proxy route traffic to your Azure DevOps instance.

Registration

Catalog descriptor

Git

By specifying the x-cortex-git field in your Cortex Catalog Descriptor, you'll be able to see Git information in the entity page, including the top language, recent commits, and top contributors.

x-cortex-git:
azure:
project: <project-name>
repository: <repository-name>
basepath: myService # optional
FieldDescriptionRequired
projectThe name of the project as listed under the "Projects" tab when you are logged into Azure DevOps (on the https://dev.azure.com/{your-organization}/ screen)true
repositoryThe repo name you see when you navigate to the "Repos" section of Azure DevOpstrue
basepathIf the entity is in a monorepo (e.g. in a subdirectory), use this field to define the subdirfalse