Quick Notes130 words
Quality and release gates — quick notes
Quality and release gates — quick notes
| Boundary | Mechanism | Set by |
|---|---|---|
| Pull-request completion | Branch policies | Project Administrators or users with repository-level Edit policies permission |
| Consume a protected resource | Approvals and checks | Resource owner |
Branch policies can require: reviewers · linked work items · resolved comments · successful build · external status checks.
Governance checks: Required template on the resource or environment · Branch control across linked-resource branches · Query Azure Monitor alerts when no queried alert rules are active · Evaluate artifact for container image artifacts.
Trap: branch policies govern PR completion; checks govern whether a stage may consume a protected resource. Different boundaries, different owners.
Primary sources
- https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-400
- https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies
- https://learn.microsoft.com/en-us/azure/devops/pipelines/process/approvals
- https://learn.microsoft.com/en-us/azure/devops/pipelines/process/resources