Eido Build can work on repositories in Azure DevOps Repos and read builds from Azure Pipelines. It signs in to Azure DevOps as a managed identity, so there is no personal access token to create or renew.
You can set this up at any time after installing. The installation itself creates nothing for Azure DevOps.
Connect Azure DevOps#
You need somebody who administers the Azure DevOps organisation.
-
Find the identity
Go to Admin → Integrations → Azure DevOps. The screen names the managed identity Eido Build signs in as. This is Eido Build’s own identity, unless you create one just for Azure DevOps with the commands the screen gives.
-
Add it to Azure DevOps
In Azure DevOps, your administrator adds that identity as a user with Basic access, and adds it to the Contributors group of each project Eido Build will work on.
-
Add the organisation
Back in Eido Build, add your Azure DevOps organisation.
-
Check
Press Check. Eido Build names anything that is missing.
Then point a project at its repository in Projects.
Workbenches#
Projects whose repositories are in Azure DevOps run on Foundry workbenches. See Workbenches.
What the identity needs#
| In Azure DevOps | Why |
|---|---|
| Basic access | To use Repos and Pipelines at all. |
| Contributors, on each project | To create branches, push, and open and complete pull requests. |
Your branch policies still apply. A pull request Eido Build opens needs the same reviewers as anybody else’s.
Using GitHub and Azure DevOps together#
A project’s repository host is worked out from the repository’s address, so you can have some projects on GitHub and others on Azure DevOps in the same Eido Build.