One of our cloud build projects has just started failing to build, with the log claiming that the repo has gone over the 2GB size limit for our tier.
“postcheckoutstatus failed. Project is too large to build for this tier of service. (2.01 GB exceeds limit by 12.49 MB). See Unity ID to upgrade.”
I’m suspicious because it was working fine until today when I edited the organisation applied to the project, which necessitated adding a new ssh key to the repo (for some reason). After that, I get this size warning. Perhaps we have just tipped over the edge, but our repo host (Unfuddle) is reporting the repo size is only 1.73GB.
Curiously, we also have another project which is still building merrily away without problem, where Unfuddle reports the repo size is 2.09GB. So something strange is going on.
It sounds like changing the “org” of the project has also changed the billing plan. At the top of the project’s page you can see what the project’s current billing plan is. If it has indeed changed, whichever user created that new org will need to sign up for a billing plan, or you can transfer the project back to an org that has a billing plan.
We’re working to make it more clear how the these relationships between users, orgs, projects and billing plans work.
As for how the size of the repo is calculated – we calculate the size of all files we downloaded from source control, and try to exclude all hidden files specific to source control.
Cheers,
Patrick
Thanks Patrick. Haha yeah I’m well confused! Actually a got it working again by deleting a few unused assets in the project, so I don’t think the plan has changed. In fact, looking at the project page as you suggest, it does still say Pro.
I fell foul of the less-than-obvious link between the different services last week when I deleted a cloud build project, only to then discover that that also deletes the same project under Unity Analytics and we lost all our analytics (post about that here: Danger: Deleting cloud build project also deletes analytics - Unity Services - Unity Discussions)
Anyway, all good now.
Yeah, huh. I actually just submitted a feature request for project removal and ownership transferral because I have this same problem and removing myself (owner) from a project didn’t seem to do anything.
http://feedback.unity3d.com/suggestions/project-management-removal-and-ownership-transfer