VisualStudio.com Repositories¶

Note

VisualStudio.com 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 VisualStudio.com repositories. Existing commits in a repository can be browsed and put up for review.

The following types of Assembla repositories are supported:

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. If you’re using TFS, this is a requirement.

Adding the Repository¶

To configure a VisualStudio.com repository, first proceed to add the repository and select VisualStudio.com from the Hosting type field.

Step 1: Link Your VisualStudio.com Account¶

You will need to link an account on VisualStudio.com to Review Board, so that Review Board can access content from the repository. If you’ve already linked an account with sufficient access to the repository, you can use that instead.

If you’re linking for the first time, you’ll need to make sure you have your username and password handy.

Fill out the following fields:

Account username:

The username used to log into your VisualStudio.com account. This is not your e-mail address.

Account password:

The password used to log into your VisualStudio.com account.

Due to the way the VisualStudio.com API and repositories must be accessed, your password will be stored in encrypted form in the database.

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:

VisualStudio.com account name:

The account name for your team. This is the my_account in https://my_account.visualstudio.com/.

VisualStudio.com project name:

The name of your project on VisualStudio.com.

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

VisualStudio.com repository name:

The name of your Git repository on VisualStudio.com.

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

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 VisualStudio.com 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 VisualStudio.com’s 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.