Question

Your team maintains 12 microservice repositories that each use an Azure DevOps YAML pipeline. Every pipeline duplicates the same 60 lines of build, test, and container-push logic. You want to centralize this logic so a single change updates all pipelines, while allowing each repo to pass its own service name and target registry. You also need to prevent a consuming pipeline from injecting arbitrary shell commands into the shared logic through the values it passes. Which approach best meets these requirements?

Accepted Answer

Create an extends template in a shared repository that defines typed parameters for the service name and registry, and reference it from each pipeline using the repositories resource.

Answer

Copy the shared steps into an includeable stage template and have each pipeline pass values using runtime variables read with the macro syntax $(var) inside script steps.

Answer

Store the shared logic in a variable group in a library and expand it into each pipeline at queue time using the variables keyword.

Answer

Define the shared logic as a task group in the classic editor and link it from each YAML pipeline via the taskGroup reference.