Integrate a repository with Azure Boards

Integrating a repository with Azure Boards is a crucial step in streamlining your work tracking system in a DevOps environment. In this article, we’ll guide you through the process of seamlessly integrating your repositories with Azure Boards part of the examination: “AZ-400 Designing and Implementing Microsoft DevOps Solutions”.

Benefits of Repository Integration with Azure Boards

Integrating your repository with Azure Boards offers numerous advantages:

1. Improved Traceability: It allows you to create links directly from your code commits or PRs (Pull Requests) to work items thus enhancing traceability.
2. Automated Status Updates: You can automate the updating of work item statuses based on commits or PR actions.
3. Streamlined Workflow: It helps in visualizing code development progression in association with the related work items all in a single place.

Supported Repositories

Azure Boards provides support for integration with a variety of repositories:

• Azure Git Repos
• GitHub
• BitBucket Cloud
• GitHub Enterprise Server
• Azure Git Repos via Azure Pipelines or GitHub Actions

Steps to Integrate Repositories with Azure Boards

In this tutorial, we are going to focus on the integration of Azure Git Repos with Azure Boards, as it is the most common scenario for the AZ-400 exam.

1. Connect Your Repo to Azure Boards

   Start by selecting the project settings icon located in the bottom-left corner of your Azure Boards project dashboard. Under the “Boards” tab, choose the “GitHub connections” or “Azure Repos/TFVC” as per your requirement. Follow the prompts to connect to your desired repo.

2. Configure Settings for Integration

   This depends on the type of repository you are connecting. For Azure Git Repos, under your Repository Settings, you will find an option “Work Item Integration”. Here you can choose how you want to link your commits or PRs to work items, and when you want to automatically update work item status.

3. Linking Commits and PRs to Work Items

   After you have your repo integrated, you can start linking your commits, PRs to work items by mentioning the ID of the work item in the commit message.

   Example code:

   git commit -m "Fixed bug, Fixes #12345"

   In this commit message, `#12345` is the ID of the work item in Azure Boards.

4. Automating Status Updates of Work Items

   Azure Boards will update work item status based on some predefined rules. For instance, if you create a PR and link it to a work item, Azure Boards will automatically set the status of that item to ‘Active’.

5. View Your Changes in Azure Boards

   Once your commits or PRs are part of the main branch, you can see these changes in Azure Boards. Click on the Boards > Work Items, select any work item, and you will find “Development” section on its details pane, it displays all the commits or PRs that are linked to this work item.

In conclusion, properly integrating your repositories with Azure Boards can transform your work tracking system to be more organized and efficient. It can significantly increase traceability and automate mundane tasks, thus freeing up time and resources for more critical tasks. Following the steps and pointers in this guide can help you take a step in the right direction towards successful DevOps workflow management.

Practice Test

True or False: Azure Boards integrates with repositories in GitHub and Azure Repos.

• True
• False

Answer: True.

Explanation: Azure Boards indeed integrates with both GitHub and Azure Repos to provide comprehensiveness to DevOps lifecycle.

To establish the integration between Azure Boards and Git repositories, which of these must you obtain from Azure DevOps?

• A. Personal Access Token
• B. Azure Boards Code
• C. Repository Key
• D. User Profile Key

Answer: A. Personal Access Token

Explanation: Personal access token is key to establish integration as it provides required authentication and access control.

Which of the following tasks or activities can be tracked using Azure Boards?

• A. Creating feature branches in GitHub.
• B. Reviewing pull requests on GitHub.
• C. Managing tasks and boards.
• D. All of the above.

Answer: D. All of the above.

Explanation: Azure Boards allows tracking of all the mentioned activities as part of its integration with repositories.

Is it true that the integration between Azure Boards and Azure Repos is enabled only for Team Foundation Version Control (TFVC)?

• True
• False

Answer: False.

Explanation: The integration is not only for TFVC, it can be established with Git repositories in Azure Repos.

Which tool can be used to link GitHub commits and pull requests to Azure Boards work items?

• A. Azure DevOps Server
• B. Azure Boards App for GitHub
• C. Azure Boards Connector
• D. Azure Repos

Answer: B. Azure Boards App for GitHub

Explanation: Azure Boards App for GitHub enables linking of GitHub commits and pull requests to Azure Boards work items.

Which of the following is NOT a benefit of integrating a Repository with Azure Boards?

• A. Centralized version control
• B. Enhanced collaboration between teams
• C. Reduced code stability
• D. Better tracking of project activities

Answer: C. Reduced code stability

Explanation: Integration with Azure Boards does not reduce code stability, but rather enhances it as progress is closely tracked.

True or False: Work items in Azure Boards can be updated automatically when there are changes in GitHub.

• True
• False

Answer: True.

Explanation: Work items in Azure Boards can be updated automatically based on the commit comments and pull request details in GitHub.

What Automation capabilities are enabled with the integration of Azure Boards?

• A. Automated builds
• B. Automated releases
• C. Automated project tracking
• D. All of the above

Answer: D. All of the above

Explanation: All of the above automations can be enabled as a part of this integration.

Which of the following is important to setup the integration of Azure Boards with GitHub Enterprise Server account?

• A. GitHub Personal Access Token
• B. Azure Boards Key
• C. Azure Boards Token
• D. None of the above

Answer: A. GitHub Personal Access Token

Explanation: The setup requires the GitHub Personal Access token to authenticate the connection.

True or False: You cannot link the existing GitHub commits and pull requests to Azure Boards work items.

• True
• False

Answer: False

Explanation: Existing GitHub commits and pull requests can be linked to Azure Boards work items using ‘#AB{ID}’.

Interview Questions

Q1: What is Azure Boards?

A1: Azure Boards is a service by Microsoft Azure that provides work tracking with Kanban boards, backlogs, team dashboards, and custom reporting to help teams plan, track, and discuss work across the entire development process.

Q2: What is a repository integration in Azure Boards?

A2: Repository integration in Azure Boards allows you to track your code commits and pull requests directly in Azure Boards. This integration creates links between your code commits and pull requests to work items.

Q3: How do you integrate a Git repository with Azure Boards?

A3: To integrate a Git repository with Azure Boards, you need to use the “@AB# id” syntax in your commit messages or pull request descriptions. The “id” refers to the work item ID you want to associate with your commit or pull request.

Q4: Can third-party Git repositories be integrated with Azure Boards?

A4: Yes, Azure Boards supports integration with popular Git repositories like GitHub, Bitbucket Cloud, and other Git providers through the use of Azure Boards app available for these providers.

Q5: What is the purpose of the ‘#AB’ syntax during the integration process?

A5: The ‘#AB’ syntax is used to create a link between your work items in Azure Boards and your code in your integrated Git repository. It allows you to track your work directly from your code.

Q6: How do you manage the state of your work items during a pull request?

A6: In a pull request, you can manage your work items’ state by using a special syntax in your pull request. For example, you can use “Fixes AB# id” to close a work item once your pull request is completed.

Q7: Can Azure Boards integrate with multiple repositories?

A7: Yes, Azure Boards can integrate with multiple repositories. You can link your work items to commits and pull requests across different repositories.

Q8: Is it possible to manually link a commit or pull request to a work item in Azure Boards?

A8: Yes, it is possible to manually link a commit or pull request to a work item in Azure Boards. This can be done from the Links tab of the work item form.

Q9: Can repository integration in Azure Boards provide traceability?

A9: Yes, repository integration in Azure Boards provides traceability for your commits and pull requests. It enables you to view the details and status of your code from the work item.

Q10: Where can you find the Azure Boards app to integrate with GitHub?

A10: The Azure Boards app for GitHub can be found in the GitHub Marketplace. After installing the Azure Boards app, you can connect one or more GitHub repositories to your Azure Boards project.

Q11: How do you integrate a Bitbucket Cloud repository with Azure Boards?

A11: To integrate a Bitbucket Cloud repository with Azure Boards, you need to install the Bitbucket Cloud app from the Atlassian marketplace, and then connect it to your Azure Boards project.

Q12: Which types of work items can be linked to commits and pull requests in Azure Boards?

A12: All types of work items can be linked to commits and pull requests in Azure Boards. This includes bugs, user stories, tasks, features, and more.

Q13: Can you unlink a work item from a commit or pull request in Azure Boards?

A13: Yes, you can unlink a work item from a commit or pull request in Azure Boards. You can do this by navigating to the Links tab of the work item form and deleting the corresponding link.

Q14: What happens when you link a work item to a commit or pull request in Azure Boards?

A14: When you link a work item to a commit or pull request in Azure Boards, a link is created that leads to this commit or pull request. This enables you to easily navigate from your work items to your code.

Q15: How does Azure Boards support traceability in DevOps?

A15: Azure Boards supports traceability by linking work items to commits or pull requests in your Git repository. This enables you to track your work and view the status and details of your code from your work items, providing complete traceability across your DevOps lifecycle.