This article addresses the issue of builds that timeout after an exceptionally long period (relative to the projects average build time). It explains how the default build timeout can be configured per project to prevent extended build times on stuck builds. The timeout interval can be manually set using the Rest API and is not available via the Dashboard. Setting a specific build timeout can help save valuable build minutes by canceling stalled builds earlier.
Symptoms:
- Builds are automatically cancelled after running for an exceptionally long time (relative to the project/target average).
- No option found in the UBA dashboard to configure build timeout.
Cause:
The default build timeout in Unity Build Automation is set to 24 hours, and there is no option to configure it through the UBA dashboard; only via the REST API. While other mechanisms exist to prevent stalled builds, builds will generally run much longer than the project's average when stalled.
Resolution:
To configure the (optional) build timeout for a project:
1. Use the Rest API to set the 'buildTimeOutMinutes' parameter in the Update Project Details endpoint.
2. That setting defines the maximum number of build minutes before the build is automatically canceled.
3. Refer to the API documentation for detailed instructions on setting this parameter.