Requires a passing pipeline run on a pull request's pre-merge result before completion, valid until its build expiration lapses; an Azure Repos branch policy.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Build validation in context, with comparison tables and the common traps.
Terms in this definition
- Pipeline
Groups activities logically so that, together, they move and transform data, either one after another or side by side; found in both Azure Data Factory and Microsoft Fabric.
- Pull request
In Azure Repos or GitHub, a proposal to merge one branch into another, at which point reviewers and branch policies or protection rules come into play.
- Build expiration
Decides how long a passing pull request build stays valid once the target branch moves on: never expiring, a number of hours, or expiring at once.
- Azure Repos
Azure DevOps' version control: Git (and legacy centralised TFVC), guarded by branch permissions and policies. GitHub's counterpart is its repositories.
- Exclusions
Scopes taken out of a policy assignment; they can only narrow its coverage, never widen it.
Related terms
- Branch policies
Requirements a pull request must meet on an Azure Repos branch, such as minimum reviewers, resolved comments, linked work items, status checks and build validation. GitHub offers rulesets and branch protection rules for this.
- Defender for Cloud pull request annotations
DevOps security comments on IaC problems, posted only against the lines a pull request changes, in GitHub or Azure DevOps. Defender CSPM is a prerequisite; on Azure DevOps you also need Contributor or Owner rights and a Build Validation policy on main.