With the beta over the unity cloud build servers have started enforcing the size limit based on your subscription plan. I've run into a situation where the execution of the plans do not seem to match with the description of the plans. In my case I'm using bitbucket which reports my git repo as 1GB, correlating with the size of my local repo as reported by 'git count-objects - v' The project files in my working copy totals to 1.7GB - excluding the .git folder I'm on the Pro Plan which should accommodate a repo size of up to 2GB yet my builds fail with the following error message: ! postcheckoutstatus failed. Project is too large to build for this tier of service. (2734132126 bytes exceeds limit by 734.132126 bytes). See https://build.cloud.unity3d.com/plans/ to upgrade. It seems like the size being tested is the total folder size (ie repo and working copy combined) The list at https://build.cloud.unity3d.com/plans/ specifically states that the limit is based on 'The size of your repository.' If the description is accurate the check should be evaluating the size of the repo itself without the working copy. Alternatively the description should at least be expanded to clarify that it's the combined size of the repo and the working copy. Hope this helps anyone else confused by this disparity.