Question

Your team maintains a monorepo in Cloud Source Repositories containing a payment microservice. You must ensure that unit and integration tests run automatically only when a pull request targets the 'main' branch, and that a container image is built and pushed to Artifact Registry only after a commit is merged into 'main'. Developers frequently open feature branches, and you want to avoid running the full test-and-build pipeline on every feature branch push. Which approach best implements this using Cloud Build triggers?

Accepted Answer

Create a pull request trigger with a branch filter matching '^main$' that runs the test-only build config, and a separate push trigger with a branch filter matching '^main$' that runs the build-and-push config.

Answer

Create a single push trigger with no branch filter and use inline bash conditionals in cloudbuild.yaml to decide whether to test or build based on the branch name.

Answer

Create one push trigger filtered to all branches that always runs tests, and rely on Artifact Registry cleanup policies to delete images that came from feature branches.

Answer

Create a scheduled trigger that runs every hour to test and build the latest commit on 'main', ignoring pull request events entirely.