Heplon

Connect Azure DevOps

This guide covers what to put into the connector form for Azure DevOps. One connector reads one organisation: every project in it, its repositories, and its Azure Pipelines builds.

1. Create a personal access token

Sign in to Azure DevOps with an account that can see the projects you want Heplon to read. Heplon reads exactly what this account can reach.

Open User settings (next to your avatar) and select Personal access tokens, then New Token.

SettingValue
Namean arbitrary name, for example heplon
Organizationthe organisation you want to connect
Expirationyour choice, see the note below
Scopesselect Custom defined, then the two rows below

Select Show all scopes to see both rows:

  • Code — Read
  • Build — Read

Create the token and copy it.

2. Fill in the form

In Heplon, open Connectors, select Add connector, then Azure DevOps.

FieldValue
Namean arbitrary name
Organisation URLhttps://dev.azure.com/$ORG, where $ORG is your organisation
Access tokenthe token from step 1

Azure DevOps is now connected to Heplon.

Notes

  • The connector stops to work when the token expires. Create a new token and edit the connector to store it.
  • For a self-hosted Azure DevOps Server, use the collection URL, for example https://azuredevops.example.com/DefaultCollection. The server must be Azure DevOps Server 2022 or later, because Heplon calls REST API version 7.1.
  • The Heplon server must be able to reach the organisation URL.