To connect to your instance of Azure DevOps (ADO) Server, you'll need to generate a Personal Access Token (PAT) with appropriate permissions, and provide this when adding the connection in Gearset.
Getting a Personal Access Token
Navigate to your ADO Instance in a browser, open user settings and select
Personal access tokens.
You should now be in the Personal Access Tokens sections, once there, select
New Token, and give your token a name.In order for the connection from Gearset to work, you will need to select
All accessible organizationsin theOrganizationdropdown.
In this example, we've selected
Full accessscope. You can also selectCustom defined, but please note that if certain permissions are not set correctly, Gearset won't work as expected.
Setting up the connection in Gearset
From the Source control and services page in Gearset select
Connect to Azure DevOps Server.
Now you should see a modal dialog, allowing you to enter the URL of your ADO Server instance, and the PAT you generated earlier.
Test your connection, and you should see the connection succeeded.
If the connection fails, make sure you're using a Personal Access Token that provides correct permissions (see above).
If you're still experiencing failed connections, contact our support via in-app chat and we'll be able to investigate the cause of the connection issues.
A note on ADO work items
Please note that Gearset currently supports linking ADO work items, but this functionality is limited to ADO Cloud organizations. Support for work items in ADO Server (self-hosted instances) is not currently available.