Question

Your team's Azure Pipelines YAML pipeline lives in the 'app' repository but must also build shared code from a separate 'shared-libs' repository in the same Azure DevOps project. You need the pipeline to (1) check out both repositories into the working directory during the build, and (2) automatically queue a new run whenever the 'main' branch of 'shared-libs' is updated. Which YAML configuration meets both requirements?

Accepted Answer

Define a 'resources.repositories' entry for 'shared-libs' with a 'trigger' on the main branch, and add a 'checkout' step referencing that repository resource.

Answer

Add a 'checkout: shared-libs' step and rely on the default 'trigger' section, which automatically watches all referenced repositories.

Answer

Configure a 'pr' trigger for 'shared-libs' under 'resources.repositories' and add a 'checkout: self' step for the shared repository.

Answer

Use a pipeline resource ('resources.pipelines') pointing to 'shared-libs' with a 'trigger: true' and a 'download' step to retrieve its source.