Import your Azure DevOps repositories
Astrolabe reads the catalog-info.yaml file of your Azure DevOps repositories and adds them to the
catalog.
You set it up once, as an administrator.
Before you start
The catalog reads Azure DevOps with the token of the Azure DevOps integration. Add it first: see Add the Azure DevOps integration.
Until it is added, the Azure DevOps card of Administration › Catalog is greyed out, with Configure the azure integration first: without it, this provider cannot read anything.
🔧 Configure the Azure DevOps provider
-
In the left sidebar, at the bottom, click Administration.
-
Under PLATFORM, click Catalog. The Providers tab opens.
-
On the Azure DevOps card, click Configure.
-
In Host, keep the host of your integration, for example
dev.azure.com. -
Fill in the other fields.
Field What to enter Example Organization The organization, as in https://dev.azure.com/<organization>.acmeProject The project to scan. *for every project of the organization.*Repository The repositories to scan. *for all, or a prefix followed by*.*Path Where the descriptor file sits in each repository. /catalog-info.yamlBranch Optional. The branch to read the descriptor from. Empty: each repository's default branch. main -
Click Install.
The window Reloading configuration says Please wait while the instance is reloading.... Then the page comes back.
Hover the ? next to a field to see what it expects, with an example.
▶️ Run the collection now
The catalog reads Azure DevOps every 30 minutes. You don't want to wait?
-
On Administration › Catalog, find the Catalog collection table.
-
On the row that starts with Azure DevOps, click Run the Azure DevOps collection now in the Actions column.
-
Wait half a minute, then reload the page. State shows the result of the run, and Detail says why when it failed.
Your repositories are then in Catalog. This step was not checked on a live instance.
✅ That's it!