Azure DevOps Server Integration

1. Log in to Collaborator as administrator. (To integrate with Azure DevOps Server repositories, you need administrator privileges in Collaborator).

2. On the Collaborator main toolbar, click ADMIN, and then select Repository Hosting Services from the tree on the left. Then switch to the Easy Add Repository tab.

3. On the tab, select Azure DevOps Git in the Add repository for box and click Next:

   

   Click the image to enlarge it.

4. Collaborator will displays a page with connection details.

   Fill in the edit boxes:

   

   Click the image to enlarge it.

   Setting	Description
   Host name	Optional. Specifies the host name where your Azure DevOps Server resides. For example dev.azure.com, myorg.visualstudio.com, or URI of your on-premise server. If host name is omitted, dev.azure.com will be used.
   Username	Required. Specifies the account name to use for authentication.
   Personal access token	Required. The personal access token for a Azure DevOps Server account that has access to your remote repository. This is the token that we generated in Azure DevOps Server earlier.
   Organization name	Specifies the name of your organization account. Required for dev.azure.com and on-premise hosts.
   Override existing configurations	Optional. Specifies whether to override existing configurations that track the same repository URI.
   Branches to track	Optional. The names of branches to track changes and create reviews on pull requests and direct pushes. Separate multiple branch names with commas. You can use Java-style regular expressions to match specific branch names, or you can use the * wildcard (alone, or separated by commas) to match all branches. Note that wildcards and regular expressions cannot be used if you enable the Status check required setting (see below). If this edit box is empty, the branch main will be tracked.
   Ignore pushes for branches	Optional. Specifies branches for which Collaborator will not create reviews on direct pushes. You can enter one or several branch names. Separate multiple branch names with commas. You can also use Java-style regular expressions to match specific branch names, or you can use the * wildcard (alone, or separated by commas) to match all branches. Note that wildcards and regular expressions cannot be used if you enable the Status check required setting (see below).
   Status check required	Specifies if Collaborator should enforce status checks for the tracked branches before merging pull requests. If this option is enabled, you cannot use regular expressions in the Branches to track setting, since this option requires exact name match.
   When review cancelled/deleted/rejected	Optional. Specifies an action to perform when a review corresponding to a pull request was cancelled, deleted or rejected: Value Description Do nothing Do not perform any action. Abandon pull request Abandon pull request that matches the review. Abandon pull request and delete its branch Abandon pull request that matches the review and delete the corresponding branch.
   When review completed	Optional. Specifies an action to perform when a review corresponding to a pull request was accomplished: Value Description Do nothing Do not perform any action. Complete pull request Complete pull request that matches the review. Complete pull request and delete its branch Complete pull request that matches the review and delete the corresponding branch. Abandon pull request Abandon pull request that matches the review. Abandon pull request and delete its branch Abandon pull request that matches the review and delete the corresponding branch.
   Reopen a review when	Optional. Specifies in what cases Collaborator should reopen completed reviews. May include any combination of the following: when a push to a pull request is made, when a comment is added to a pull request.
   Wait for signature (if enabled) before merge	Optional. Effective, if "When review completed" setting is set to "Merge the pull request" or "Merge the pull request and delete its branch". If enabled Collaborator will wait for the completed review to be signed off before merging the respective pull request. Otherwise, pull request will be merged immediately, even if the review have not been signed yet.
   Auto close related work items	Automatically complete related work items when pull request is merged.
   Auto assign reviewers	Whether to assign Collaborator reviewers when some specific users were added as pull request reviewers on the Azure DevOps side and integration can match those Azure DevOps users with Collaborator users.

5. After you specified the settings, click Load repositories. This will display a list of repositories available for the specified user account or organization in Azure DevOps Server. Select the repositories to track and click Create for selected. To stop suggesting integrations for some specific repositories, select these repositories in the list and click Ignore selected.

   Alternatively, you can click Create for all and use the settings for all repositories that are available for the specified user account or organization in Azure DevOps Server. Collaborator will create an individual configuration for each repository, and, if needed, will create a webhook for each repo in Azure DevOps Server.

1. Log in to Collaborator as an administrator. (To configure integration settings, you need administrator privileges in Collaborator).

2. On the Collaborator main toolbar, click ADMIN, and then select Repository Hosting Services from the tree on the left. Then switch to the Configure Remote Systems tab.

3. In the New Remote System Configuration section, select Azure DevOps Git and click Create:

   

   Click the image to enlarge it.

4. Collaborator will display a page with configuration settings. Specify the setting values:

   Setting	Description
   Title	Required. The configuration name as it will be displayed in Collaborator user interface.
   Azure DevOps repository URI	Required. The URI of the Azure DevOps repository to be tracked, for example, https://dev.azure.com/myorg/myproject/_git/myrepo or https://myorg.visualstudio.com/myproject/_git/myrepo. You can copy the URI from the repository page in Azure DevOps Server:
   Username	Required. Specifies the account name to use for authentication.
   Personal access token	Required. The personal access token for a Azure DevOps Server account that has access to your remote repository. This is the token that we generated in Azure DevOps Server earlier.
   Branches to track	Optional. The names of branches to track changes and create reviews on pull requests and direct pushes. Separate multiple branch names with commas. You can use Java-style regular expressions to match specific branch names, or you can use the * wildcard (alone, or separated by commas) to match all branches. Note that wildcards and regular expressions cannot be used if you enable the Status check required setting (see below). If this edit box is empty, the branch main will be tracked.
   Ignore pushes for branches	Optional. Specifies branches for which Collaborator will not create reviews on direct pushes. You can enter one or several branch names. Separate multiple branch names with commas. You can also use Java-style regular expressions to match specific branch names, or you can use the * wildcard (alone, or separated by commas) to match all branches. Note that wildcards and regular expressions cannot be used if you enable the Status check required setting (see below).
   Status check required	Specifies if the integration should enforce status checks for the tracked branches before merging pull request. If this option is enabled, you cannot use regular expressions in the "Branches to track" setting, since this option requires exact name match.
   When review completed	Optional. Specifies an action to perform when a review corresponding to a pull request was cancelled, deleted or rejected: Value Description Do nothing Do not perform any action. Complete pull request Complete pull request that matches the review. Complete pull request and delete its branch Complete pull request that matches the review and delete the corresponding branch. Abandon pull request Abandon pull request that matches the review. Abandon pull request and delete its branch Abandon pull request that matches the review and delete the corresponding branch.
   When review cancelled/deleted/rejected	Optional. Specifies an action to perform when a review corresponding to a pull request was cancelled, deleted or rejected: Value Description Do nothing Do not perform any action. Abandon pull request Abandon pull request that matches the review. Abandon pull request and delete its branch Abandon pull request that matches the review and delete the corresponding branch.
   Reopen a review when	Optional. Specifies in what cases Collaborator should reopen completed reviews. May include any combination of the following: when a push to a pull request is made, when a comment is added to a pull request.
   Wait for signature (if enabled) before merge	Optional. Effective, if "When review completed" setting is set to "Merge the pull request" or "Merge the pull request and delete its branch". If enabled Collaborator will wait for the completed review to be signed off before merging the respective pull request. Otherwise, pull request will be merged immediately, even if the review have not been signed yet.
   Auto close related work items	Automatically complete related work items when pull request is merged.
   Auto assign reviewers	Whether to assign Collaborator reviewers when some specific users were added as pull request reviewers on the Azure DevOps side and integration can match those Azure DevOps users with Collaborator users.
   Webhook status	Indicates the current status of the webhook: Status Description Webhook is absent The webhook has not been created yet. Webhook isn't active The webhook has been created, but is inactive. Up and running The webhook is active.

5. To create or activate a webhook, click Update webhook.

   Important: Click this button, when you set up integration with your repository for the first time.

   To learn more about webhook settings on the Azure DevOps Server side, see Microsoft documentation:

   https://docs.microsoft.com/en-us/azure/devops/service-hooks/services/webhooks?view=azure-devops

6. Click Test Connection to verify if you entered data correctly.

   Click Save to store the settings.

Sections above describe how to add integrations for existing repositories. When some new repositories are created on a server, you may integrate them manually. Alternatively, you can setup Azure DevOps auto-polling configuration that will periodically look for new repositories on the specified server, user or project and suggest creating integrations for them.

1. Log in to Collaborator as administrator. (To integrate with Azure DevOps repositories, you need administrator privileges in Collaborator).

2. On the Collaborator main toolbar, click ADMIN, and then select Repository Hosting Services from the tree on the left. Then switch to the Repository Auto-Polling tab.

3. On the tab, select Azure DevOps in the Add configuration box and click Next.

4. Collaborator will displays a page with connection details.

   

   Click the image to enlarge it.

   Fill in the edit boxes:

   Setting	Description
   Username	Required. Specifies the account name to use for authentication.
   Server URI	Required. The URI of Azure DevOps server, user or project to be polled for new repositories.
   Token	Required. The personal access token for a Azure DevOps Server account. This is the token that we generated in Azure DevOps Server earlier.

   After specifying these values, you can click Test connection to verify if you entered data correctly.

5. After you specified the values, click Save. This will create an auto-polling configuration and display it in the Auto-Polling Configurations List.
6. Scroll down the Repository Auto-Polling tab and check that the Enable Auto-Polling setting is on and optionally change the Auto-Polling Interval setting.

Now Collaborator will automatically check if any new repositories were found on the specified server. Once found, it will notify administrators and suggest creating integrations with these newly created repositories via the Easy Add Repository wizard.