You are using Cloud Build to build a Docker image. You need to modify the build to execute unit and run integration tests. When there is a failure, you want the build history to clearly display the…

Question

Options

• AAdd RUN commands in the Dockerfile to execute unit and integration tests.
• BCreate a Cloud Build build config file with a single build step to compile unit and integration tests.
• CCreate a Cloud Build build config file that will spawn a separate cloud build pipeline for unit and
• DCreate a Cloud Build build config file with separate cloud builder steps to compile and execute

• A
  11% (4)
• B
  6% (2)
• C
  3% (1)
• D
  81% (29)

Explanation

Creating a Cloud Build config file (cloudbuild.yaml) with separate, discrete build steps for compiling, unit testing, and integration testing is the best approach. Each step runs in its own container and is recorded independently in the build history. When a failure occurs, Cloud Build marks exactly that step as failed, making it immediately visible which stage broke. Adding RUN commands in the Dockerfile (A) bundles everything into one opaque layer. A single build step (B) loses granularity - a failure anywhere shows as one undifferentiated failure. Spawning a separate pipeline (C) adds unnecessary complexity and makes tracing failures harder, not easier.

No community discussion yet for this question.