Question

Your team builds a container image in a dedicated CI pipeline that publishes a versioned artifact. A separate release pipeline (defined in a different repository) must automatically run only when the CI pipeline completes successfully on the main branch and produced a build tagged 'production-ready'. You want the release pipeline to consume the completed run's artifacts without polling or manual triggering. Which YAML construct in the release pipeline should you configure?

Accepted Answer

A 'resources.pipelines' entry referencing the CI pipeline with a 'trigger' that filters on the 'main' branch and the 'production-ready' tag

Answer

A 'resources.repositories' entry pointing at the CI repository with a 'trigger' on the main branch

Answer

A scheduled 'cron' trigger that runs every 15 minutes and downloads the latest artifact if a new one exists

Answer

A 'ci trigger' with a 'batch: true' setting and a 'paths' include filter for the CI pipeline's output folder