Azure DevOps Services Repositories¶

Note

Azure DevOps Services support requires a license of Power Pack. You can download a trial license or purchase a license for your team.

Review Board supports posting and reviewing code on Azure DevOps Services (formerly Visual Studio Team Services and Visual Studio Online) repositories. Existing commits in a repository can be browsed and put up for review.

The following types of repositories are supported:

Git
TFVC

To simplify posting changes to Review Board, we recommend using RBTools. This ensures that the diffs are in the correct format, and makes managing review requests much easier.

Adding the Repository¶

To configure an Azure DevOps Services repository, first proceed to add the repository and select Azure DevOps Services from the Hosting service field.

Step 1: Link Your Azure DevOps Services Account¶

In order for Review Board to connect to your Azure DevOps Services account, you need to create a Personal Access Token. From your account on https://dev.azure.com, click on the User settings icon in the upper right, then choose Personal access tokens from the menu. The token will need the Full scope under the Code section.

Then in the Review Board repository configuration, fill out the following fields:

Account username:: The username used to log into your Azure DevOps Services account. This may be left blank.
Account password:: The Personal Access Token that you configured.

The account will be linked when the repository is saved. If there are errors authenticating the user or retrieving an access token, you will be prompted to fix them.

Step 2: Provide Repository Information¶

Next, you’ll need to fill out the following fields:

Repository type:

Choose Azure DevOps / TFS (Git) for Git repositories or Azure DevOps / TFS (TFVC) for TFVC repositories.

Azure DevOps organization name:

The organization name for your team. For example, if your URL is https://dev.azure.com/example (or the legacy https://example.visualstudio.com), enter example.

Azure DevOps project name:

The name of your project. For example, if your clone URL is:

https://MyOrganization@dev.azure.com/MyOrganization/MyProject/_git/MyRepo

Then your project name would be MyProject.

This is only required for Git repositories, and is not used for TFVC.

Azure DevOps repository name:

The name of your repository. For example, if your clone URL is:

https://MyOrganization@dev.azure.com/MyOrganization/MyProject/_git/MyRepo

Then your repository name would be MyRepo.

This is only required for Git repositories, and is not used for TFVC.

Step 3: Choose a Bug Tracker¶

You can specify a bug tracker on another service. At the time of this writing, support for bug trackers on Azure DevOps Services is not supported.

Learn more about bug tracker configuration.

Step 4: Manage Access Control¶

You can now choose who should have access to this repository (both posting against it and viewing review requests posted against it). This is separate from Azure DevOps Services’ own access controls.

Learn more about access control.

Step 5: Save the Repository¶

At this point, you should be able to save the repository. If saving succeeds, you’re done! You can start posting changes for review.