Your company stores their source code in a Cloud Source Repositories repository. Your company wants to build and test their code on each source code commit to the repository and requires a solution th

Question

Options

• AUse Cloud Build with a trigger configured for each source code commit.
• BUse Jenkins deployed via the Google Cloud Platform Marketplace, configured to watch for source
• CUse a Compute Engine virtual machine instance with an open source continuous integration tool,
• DUse a source code commit trigger to push a message to a Cloud Pub/Sub topic that triggers an

• A
  69% (22)
• B
  6% (2)
• C
  6% (2)
• D
  19% (6)

Explanation

Cloud Build (A) is Google Cloud's fully managed, serverless CI/CD platform that natively integrates with Cloud Source Repositories. You can configure a trigger to automatically build and test code on every commit with zero infrastructure management. Jenkins (B) requires deploying and managing VMs on GCP Marketplace. A custom Compute Engine CI setup (C) requires maintaining OS, updates, and tooling. A Pub/Sub trigger (D) would need additional orchestration logic and still requires managing compute for the build step. Cloud Build satisfies the 'managed' and 'minimal operations overhead' requirements directly.

No community discussion yet for this question.