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 Unity ID 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.
We are experiencing the exact same problems 700 MB Repo but for some reason builds to larger than 2 GB hitting the 2 GB cap. Would love to see limit increased OR a fix to only evaluate repo size only before building.
Thank you for your feedback! The size we measure is a actual snapshot of the project so without the history e.g. within the .git folder when using Git. We currently monitor the repositories and see what goes wrong.
The path you entered is probably not correct. If you use subfolders in your repositories you need to add them in Project Subfolder field in Project Settings. As a test we set it to unity as unity is included in the checkout, but we have no idea how the structure of you repository looks like. You need to specify the direct path to the directory which includes the Assets and ProjectSettings folder! Please let me know if this helps!
Are you looking at the correct project? Our Project Subfolder is already set, and it’s set to ‘unity’, and hasn’t changed since I set it up weeks ago.
The issue here is the repo is reporting a size in the error log, that it isn’t. This project built fine and without changing settings, suddenly the size was too big despite the size being 300mb.
Hi @topherr - yes, it looks like Cloud Build is seeing a much larger size than it did previously. I assume you haven’t recently committed some large files? Maybe do a “get Info” or “properties” of that repo folder and let us know what the calculated size is?
I’m running into the same issue. The repos is about 1.3GB but the build system reports it as 2.6GB, which makes me guess the .svn folder is included in the count, which isn’t what I would be expecting.
So, to confirm, Unity Cloud Build is doing a shallow pull without any history past the current state and checking the size of that, not the total size of the repository with it’s whole history in .git folders, right?
I’m currently seeing the message “3.92 GB exceeds limit by 1.92 GB”, however our full checkout of our repository data is definitely only 550 MB (I just checked). Is there anything else it takes into account rather than just your checked out assets ?
e.g.:
If building for 2 platforms, is the limit effectively halved ?
Does it take into account the size of the Library and Temp folders Unity generates whilst importing and building (i.e. those that are not in version control)?
The size is calculated from the root of the source control, so if you’re using Git or Mercurial, we’re downloading (and calculating) the file size of everything downloaded, ignoring history files. If you have source assets in the same repo but in a parallel directory, we’re still downloading them, so it still fits into the size calculation.
If you have the Library or Temp folders in source control (which you shouldn’t), they will be included in the size calculation.
If you’re using SVN or Perforce, you can configure your project such that Cloud Build only downloads the specific path that contains your Unity project. Note that the “subdirectory” field in Cloud Build is only used to mean “the subdirectory beyond the root that we download from”.
Let us know if you have questions or if the problem persists.
Thanks Patrick - I already accounted for every single folder in SVN, all the way to the root when I calculated the 550MB figure. Definitely no Library or Temp folders there.
I left it until all builds had finished, built again and the problem disappeared by itself (SVN had definitely not shrunk in the intervening time!), so I suspect it may happen again at some point even though we are below the repo size limit.
@patrickc I’m having the same problem. My folder is set right, and the entire size of my SVN repo is well below the max for my plan, but it still stops the build saying that it is too large. The weird part is that it only does this for iOS, not Android, Mac, PC, or Linux.
