Cloud Build times out after 10 minutes: raise the build timeout
Shows how to fix cloud Build times out after 10 minutes: raise the build timeout. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
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.
Steps
- 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.
When to use
You are seeing this: The accepted answer gives the mechanism: 10 minutes is the default timeout, and it is configurable per build. Use this skill when you run into "Cloud Build times out after 10 minutes: raise the build timeout".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.