Firstly, I am not sure if this has been asked before. If so, I couldn’t find it. Sorry.
So I recently got cloud build to work but I am quite worried about the max repo size. I am currently using the free plan so I only have 1GB. Now after building a build for Windows, Mac and Linux I am already up to ~90MB. It is taking up space quickly. But what happens when it reaches the max size? I can’t find a way to remove old builds to make up more space. Does it just stop working and prompt you to upgrade, does it remove old builds or something different?
I got mine working with Perforce quite nicely, but the repo size limit seems a bit aggressive. From what I can tell I think the repo limit is per project and it updates the cache for that project when you go to build (it doesn’t add a new version). I’m not 100% sure on that, but I think that’s what I’m seeing. When you hit the cap, the build just errors and fails.
My plea to the Unity team is to raise these caps because, honestly, I can have a single Photoshop file in my project that’s 200 mb… capping the repo size at 1 gb is kind of heavyhanded imo.
Hi! I’ve gone through steps to reduce repository size via BFG. I see mirrored clone of repository is significantly smaller now, so I performed pruning, GC and pushing to bitbucket. I don’t see the size in settings to reflect immediately.
Including previous builds in your repository will cause the repository size to grow pretty quickly. Which source control system are you using? There are a number of ways you could have the system ignore those builds, ideally they would be contained within a single directory that could be ignored wholesale.
When a repository exceeds the maximum size for your current plan, the build will fail and display an error message regarding the filesize.
When using Git or Mercurial, you cannot omit subdirectories located in the repository from the checkout. One way to prevent an eventual issue with your builds directory would be to remove it from your Bitbucket repository.
Another suggestion is to maintain your Unity project in its own repository, with assets and artifacts like compiled builds being stored in a separate repository. This way, those files will not count toward the filesize limit of a given plan.