Azure Repos Change Management Procedure: Configuring Git Repository for DevOps Solutions

Implementing Change Management Procedure in Azure Repos for Git Repository

Question

You use a Git repository in Azure Repos to manage the source code of a web application. Developers commit changes directly to the default branch.

You need to implement a change management procedure that meets the following requirements:

-> The default branch must be protected, and new changes must be built in the feature branches first.

-> Changes must be reviewed and approved by at least one release manager before each merge.

-> Changes must be brought into the default branch by using pull requests.

What should you configure in Azure Repos?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A

Branch policies help teams protect their important branches of development. Policies enforce your team's code quality and change management standards.

https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies

The correct answer is A. branch policies of the default branch.

Explanation: In this scenario, the goal is to implement a change management procedure that requires changes to be built and reviewed before merging into the default branch. Azure Repos offers branch policies that allow you to configure a set of rules that govern how changes are made to a branch.

To configure the branch policies for the default branch, follow these steps:

  1. Navigate to the Azure Repos repository in the Azure DevOps portal.
  2. Click on the branch you want to protect (in this case, the default branch).
  3. Click on the "Branch policies" button on the right side of the page.
  4. Under "Build validation", select the checkbox for "Require a minimum number of reviewers" and set the number of reviewers to 1. This ensures that changes are reviewed and approved by at least one release manager before each merge.
  5. Under "Merge strategy", select the option for "Only allow merge if all status checks have passed". This ensures that changes are built in the feature branches first before being merged into the default branch.
  6. Under "Merge types", select the option for "Require a pull request before merging". This ensures that changes are brought into the default branch by using pull requests.

Once you have configured the branch policies, any changes made to the default branch will be subject to the rules you have set. This helps to ensure that changes are properly tested and reviewed before being merged into the default branch, which can help to prevent issues from arising later on.