Azure DevOps

You can use the data from your commits to Azure DevOps, formerly known as Visual Studio Team Services (VSTS), to help you find and fix bugs faster.

Configure Azure DevOps

Note: Sentry owner or manager permissions, and Azure project admin permissions are required to install this integration.

  1. In Sentry, navigate to Organization Settings > Integrations.

  2. If you have the legacy VSTS integration installed, you’ll see a button next to Azure DevOps that says Upgrade. If you do not have the legacy VSTS integration installed, you’ll see a button that says Install.

    azure global install

  3. In the resulting modal, click Add Installation.

    azure global add installation

  4. An Azure DevOps install window should pop up. Select the Azure DevOps account you'd like to link with Sentry, and press Submit.

    azure global installed

Azure DevOps should now be enabled for all projects under your Sentry organization, but you'll need to configure the features below.

Commit Tracking

Commit tracking allows you to hone in on problematic commits. Learn more about commit tracking.

Suspect Commits and Suggested Assignees

Once you set up commit tracking, you’ll be able to see the most recent changes to files found in the issue’s stack trace with suspect commits.

For issues where the files in the stack trace match files included in commits sent to Sentry, you’ll see the suspect commit, with a link to the commit itself.

azure global suspect commit

You’ll also see that the author of the suspect commit will be listed as a suggested assignee for this issue. To assign the issue to the suggested assignee, click on their icon.

Issue Management

Issue tracking allows you to create Azure DevOps issues from within Sentry, and link Sentry issues to existing Azure DevOps Issues.

Once you’ve navigated to a specific issue, you’ll find the Linked Issues section on the right hand panel. Here, you’ll be able to create or link Azure DevOps issues.

azure global link issue

Issue Sync

Sync comments, assignees and status updates for issues in Sentry to Azure DevOps, to minimize duplication. When you delegate an issue to an assignee or update a status on Azure DevOps, the updates will also populate in Sentry. When you resolve an issue in Sentry, it will automatically update in Azure DevOps.

To configure Issue sync, navigate to Organization Settings > Integrations, and click Configure next to your Azure DevOps instance. On the following page, you’ll see options of what information you’d like synced between Sentry and Azure DevOps.

azure global issue sync

Resolve in Commit

Once you send commit data, you can start resolving issues by including fixes <SENTRY-SHORT-ID> in your commit messages. For example, a commit message might look like:

Copied
Prevent empty queries on users

Fixes MYAPP-317

When Sentry sees this, we’ll automatically annotate the matching issue with reference to the commit, and later, when that commit is part of a release, we’ll mark the issue as resolved.

Troubleshooting

No accounts during installation

azure add account no accounts

If you reach the account selection page during the Azure Devops installation process (step 4 in the instructions above) and see that there are no accounts available to select, please check the following possibilities:

  • Ensure you are logged into the account connected to your Azure DevOps organization.
  • Double-check that your account is a Microsoft Account (MSA).
  • For Single Sign-On, see Azure Active Directory SSO.
You can edit this page on GitHub.