如果管道单元测试失败，则将 Azure Devops Repo 还原为未合并的 state

Question

We have an Azure Pipeline that merges into a repository that converts.json files representing customer orders into C# objects. Naturally, if the design or naming of these C# objects ever changes, the old orders will become unusable, so we run a script 'Migrating' all these outdated.jsons to conform to the new model.

Our current pipeline that merges dev into production Migrates our.jsons, and we run a PowerShell unit test script after the pipeline's completion to ensure that the.jsons have successfully Migrated. We'd like to place this test into the pipeline itself, but there are two conditions we'd prefer to meet.

1. If the Test fails, not only abort the merge, but revert the.jsons to their un-Migrated versions.

2. Give us the option to continue the merge anyway, in the event that the website encounters an error so critical and urgent we are willing to bear the loss of a few quotes.

Are these conditions feasible?

Answer 1

According to your description, you may consider using Build validation as the Branch policies and settings .

Basically, let's assume your production code is in the Production branch; then you can create a Dev branch and push your new commits into the Dev branch. When setting the Build validation policy on the Production branch, the PR request will not be completed if the build fails, which contains the unit test. Therefore the new code from Dev branch will not be merged into the Production branch.

In the meanwhile, other branch policies may also help you with the code version control. Hope the following documents can help as well.

Require a minimum number of reviewers

Check for linked work items

Check for comment resolution

Limit merge types