Question

Your team maintains 12 Azure Pipelines YAML files across several microservices. Each pipeline repeats the same block of build configuration variables (build tool version, cache key prefixes, and a shared artifact retention flag). When one value changes, engineers must edit all 12 files, and drift has caused inconsistent builds. You want a single source of truth so a change is made once and consumed by every pipeline, while still allowing each pipeline to override specific values when needed. Which approach best meets these requirements?

Accepted Answer

Create a variables template YAML file in a shared repository and reference it in each pipeline with the 'variables: - template: ...' syntax, passing parameters where per-pipeline overrides are required.

Answer

Define all shared values as pipeline-level runtime parameters in each of the 12 YAML files so engineers can supply them at queue time.

Answer

Store the shared values in a single variable group and rely on the variable group's built-in inheritance to automatically apply to every pipeline in the project.

Answer

Use YAML anchors and aliases to define the variable block once at the top of each pipeline and reference it later in the same file.