You are developing a new web application using Cloud Run and committing code to Cloud Source Repositories. You want to deploy new code in the most efficient way possible. You have already created a Cl

Question

Options

• ACreate a Pub/Sub topic to be notified when code is pushed to the repository. Create a Pub/Sub
• BCreate a build trigger that runs the build file in response to a repository code being pushed to the
• CCreate a webhook build trigger that runs the build file in response to HTTP POST calls to the
• DCreate a Cron job that runs the following command every 24 hours: gcloud builds submit.

• B
  89% (24)
• C
  7% (2)
• D
  4% (1)

Explanation

Since the Cloud Build YAML file and gcloud run deploy command already exist, the most efficient next step is to automate triggering that build whenever new code is pushed. Creating a Cloud Build trigger (B) that watches the Cloud Source Repository and fires the existing build configuration on every push is the standard Google-recommended CI/CD pattern - it is event-driven, requires no extra infrastructure, and integrates natively with Cloud Source Repositories. Using Pub/Sub (A) adds unnecessary complexity. A webhook trigger (C) is designed for external Git providers (GitHub, Bitbucket), not Cloud Source Repositories. A daily cron job (D) is neither efficient nor event-driven.

No community discussion yet for this question.