Set the timeout field in cloudbuild.yaml to what the build really needs (the max is 24h); the default is only 600s. If you submit from the CLI, pass the --timeout flag, e.g. gcloud builds submit --timeout=1800s . Timeouts apply to the whole build, and individual steps can also carry their own timeout that must fit inside the build timeout. If builds keep timing out after raising it, the fix is not a bigger number but a faster build: cache dependencies and split slow steps.

Context: Stack Overflow #42727071 (accepted answer, 49 votes): a build dies at 10 minutes 3 seconds with Build failed (timeout), and the asker is fine with it taking longer. The accepted answer gives the mechanism: 10 minutes is the default timeout, and it is configurable per build.