Question

Your team's Cloud Build pipeline compiles a Go binary and produces a container image. Currently the build succeeds but downstream Cloud Deploy releases cannot find the image, and audits show the built image is never stored in a central location. You need the build to reliably publish the container image to Artifact Registry so it can be referenced by digest in later stages. Which approach correctly ensures the image is pushed and its digest is recorded?

Accepted Answer

Add the image to the top-level 'images' field in the Cloud Build config so Cloud Build pushes it to Artifact Registry and records the resolved digest in the build results.

Answer

Rely on the 'docker build' step alone, since Cloud Build automatically pushes any image tagged with an Artifact Registry hostname at the end of the build.

Answer

Store the built image as a Cloud Storage object using the 'artifacts.objects' field and have Cloud Deploy read it from the bucket.

Answer

Enable Binary Authorization on the build trigger, which will push the image to Artifact Registry as part of attestation generation.