Question

Your team maintains a large classic build definition in Azure DevOps that includes 40 tasks, several task groups shared across three other classic pipelines, and variable groups linked to Azure Key Vault. Leadership wants to migrate to YAML multi-stage pipelines while minimizing rework and preserving the shared logic across pipelines. Which approach should you take?

Accepted Answer

Convert each task group into a reusable YAML template referenced by the migrated pipelines, keep referencing the existing variable groups, and rebuild the definition as a multi-stage YAML pipeline.

Answer

Use the 'Export to YAML' option on the classic definition to generate a complete multi-stage YAML file, then delete the task groups since YAML does not support them.

Answer

Recreate the entire pipeline inline in a single YAML file per consuming pipeline, duplicating the shared task logic in each so the pipelines remain fully independent.

Answer

Leave the classic definitions in place and only wrap them by calling them from a new YAML pipeline using the 'RunPipeline' task to trigger the classic builds.