Question

Your team's Cloud Build pipeline builds a large Java microservice. Each build downloads all Maven dependencies from scratch, and the container image is rebuilt entirely on every commit, causing builds to take over 20 minutes. You want to reduce build times without changing the application source. Which approach should you implement?

Accepted Answer

Use Kaniko with a cache repository in Artifact Registry and store Maven dependencies in a Cloud Storage bucket referenced via the Cloud Build 'cache' directory between builds.

Answer

Increase the machine type of the default Cloud Build worker pool to the largest available size so more CPU is dedicated to each build.

Answer

Split the build into multiple triggers so that dependency downloads and image builds run as separate Cloud Build jobs on different branches.

Answer

Disable build provenance generation and Binary Authorization checks to remove overhead from the build steps.