Groups jobs inside an Azure Pipelines run. Before each one begins, approvals and checks are evaluated, and stages follow one another unless dependsOn says otherwise.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Pipeline stage in context, with comparison tables and the common traps.
Terms in this definition
- Azure Pipelines
CI/CD service within Azure DevOps that deploys applications and infrastructure as code, with environments, approvals and checks.
- Approvals and checks
Resource owners configure these in the web portal rather than YAML, on environments, agent pools, repositories, secure files, variable groups and service connections; a stage can't use the resource until all pass. GitHub's equivalent: environment protection rules.
- dependsOn
In an ARM template, the list of resource names or IDs (commonly built with resourceId()) to deploy before this resource. It controls sequencing only and provides no iteration.
Related terms
- Deduplication
Stripping out repeated and almost identical documents as a pipeline stage. Spark ML can do this by pairing MinHash LSH with a similarity join.
- Requirements quality widget
Dashboard tile listing requirements returned by a work item query next to the newest outcome of each one's linked tests in one selected pipeline stage, making it obvious which are failing or lack tests.