We use jenkins (https://jenkins.io/) to automate our Unity builds. We have a custom script that calls BuildPipeline.BuildPlayer and we check the return value to see if the build was successful. This has been working for us for years now. We recently upgraded to Unity 5.5.0 and we now find that sometimes BuildPlayer will return a message of “5 errors”. Nothing else in the logs indicates that there are any errors and the build actually succeeds! We haven’t been able to track down a cause for this, so right now we are just ignoring the return value of BuildPlayer. Obviously though this means we don’t see any legitimate errors either. Does anyone know why this would have started happening or how to address it? If we could find out more information about these supposed “5 errors” that could also help, but the return value from BuildPlayer is all we get.
Thanks for any help you can give!
It seems that the occlusion culling data was out of date, which is reported as an error but does not actually prevent the build from succeeding. This seems wrong IMO, either something is an error or it isn’t, and if it’s an error then the build should be aborted. We discovered this by calling our autobuild script from the editor rather than the commandline, and the errors show up in the editor console.