I have a repo/cloud build setup where builds from a new branch are taking several hours only to be cancelled, what causes cloud build to spontaneously cancel builds?
The log ends like this:
15156: [Unity] Platform modules already initialized, skipping
15157: [Unity] Script Compilation Pipeline Post Process Assets time: 72.796693s
15158: [Unity] Assembly Updater Post Process Assets time: 0.178223s
15159: Build was canceled
15160: Killing process...
15161: postbuildstatus finished successfully.
15162: postbuildsteps finished successfully
15163: Finished: CANCELED
Cloud Build cancellations are never spontaneous. Auto-cancellation happens when the build runs for too long, usually because a process has stalled.
Typically this happens in user-provided or third-party scripts since Editor devs know better than to introduce potential stalls into the build process. Unfortunately these tend to be extremely difficult to debug though since stalls are usually a side effect of a failure but do not themselves log any useful error.
See if you can determine what change was introduced to cause this, potentially by locking the Unity target version to exactly the same version as you are developing on locally. If you can’t identify the issue then we can take a look at your project if you submit a support ticket
You may want to try turning off caching.
You are right, there was a AndroidManifest conflict that wasn’t showing on the cloud build log.
Making a manual build shows errors that don’t show on cloud build.
1 Like
