Build process always checks out while repo (SVN)

It seems the build process always checks out the whole repository after a commit. I see this in every log:

Checking out a fresh workspace because there's no workspace at /BUILD_PATH/com.<rest-of-bundle-id-removed>15.53f5c0501a6c061f250009f5.default-ios

since the server is located in our network, it actually kills our network connection a little bit.

Is this normal?

Cheers,
Maurice

 

Yeah, it always finished and builds the app, but it is a relative small app and it takes 15 minutes to build it, which is mostly due to a full svn checkout (out upload speed isn't that great). It even checks it out 3 times, one for android, one for ios and one for web.

> But you can disable the auto-build option in your project settings in the platform section if it kills the
> performance of your network and trigger it manually.
​

And that is why I would love a trigger mechanism where I can trigger a build by specifying a keyword in the commit message

​

 

Could you elaborate on this? To me this seems like just a huge waste of resources on every end of the process.

 

Indeed, (at least) svn takes care of delete, add and update operations. And because you do not edit files there is no chance of conflict (and if files do get edited because of the build process you can always revert before updating)

 

It sounds like UCB is not keeping a copy of our project any longer than it has to for a specific build.

That's probably a good thing.

 

Why would that be a good thing? Because it saves them space? Surely, if a repository is being committed to more than once a week, it must be more cost-effective to store a 1GB project file than it is to download a 1GB project file anew each time. Let alone if the project is being committed to several times a day!

Would it be better because my studio's IP shouldn't reside outside my network? If that's the argument, downloading the project file each time should be an option - but it should still default to 'off'. Besides that, UT's bug reporter has been happily accepting (and, presumably, storing in perpetuity) project files for years.

 

That was indeed my point.

Yet you have made a valid counterpoint.

I've submitted several projects with bug reports but I've always created an isolated prototype to demo the bug. I've never submitted my main game project. But I suppose that many people would submit their game, especially as part of the automated crash reporter.

I wonder what Unity's policy is toward retaining projects submitted through bug reports.

As for UCB, maybe the option to cache project assets should exist for one of their paid tiers.

 

What kind of build times are you guys typically getting?

We work with quite a big GIT repo with a lot of history. After the initial checkout (the build took around 2 hours 30 mins) I thought UCB would just pull the latest changes and do a build (each time a commit was pushed). But it seems as mentioned by hypeNate that UCB clones a fresh copy each time, which is resulting into build times in excess of 2 hours each.

Is there anyway to get UCB just to pull the latest changes and not a fresh copy each time?

 

I also want a feature to pull the project, not cloning for every build. Add such an ability to the settings
UCB could also clean all local files before new push for getting rid of possible conflicts. But it will safe a lot of build time! My project build takes now more then 30 minutes. It is too long! On local machine and TeamCity it takes not more than 6 minutes!

 

We use an Amazon web service with Gitlab deployed on to it.

 

We do also have this issue. Our SVN repo (https://unfuddle.com/ & https://www.assembla.com/) is aproaching 15 GBs. Building time exceeeds 2.5 hours. Sometimes is takes 3 and more hours to build.

 

I'm wondering, is this situation still the same? This older comment implies that "clone the whole project every time" is the expected behavior, and that there is some sort of switch the UCB team can flip to turn it off in particular cases. (If this is the case, couldn't you guys simply expose the switch in our settings?) Your more recent comments/questions, though, seem to suggest that the clone behavior is being treated as a bug rather than the expected behavior, and I'm not sure which behavior - push vs clone - is expected at this point.

Our ~2.5GB repository (hosted on BitBucket) project takes more than 30 minutes to compile.

 

Our project is hosted on bitbucket (git).

 

We really need faster build time. For release build 30min-1h is ok. But our team can't wait this time for development build. I'm ready to pay you for the new feature (checkbox in settings): Pull, do not clone)
Offtop: we also need another feature: ability to check and build from more than one branches. E.g. for development we need to build project from develop branch and any branches under /feature or /test. So additionaly to develop, build server could check any other branches set up to build, e.g. under /feature. Teamcity allows it using /feature/* pattern for branches. But I want it on UCB too

 

Included a screenshot of the build info.

 

We've been trying the advanced caching feature (thanks to hypeNate) last days and build times decreased from 2.5 hours to under 1 hour. So far it's working great.

 

I noticed that this happens with Unity Cloud Build and Git while using GitHub and LFS. I make a small change and it downloads entire GBs of data. Because Github has limited bandwidth, I couldn't use their service for my game repo since Unity Cloud Build ate through the bandwidth within a few builds.

Bitbucket doesn't have bandwidth limitations (at the moment), so that seems like a better place to host a repo for use with Unity Cloud Build.

Regardless, it does seems a little strange that the entire repo needs to be downloaded each time. I thought the point of SCM systems were to prevent this waste of resources.

(Edit: Just noticed this was a big necro, but still seems to be a problem 4 years later.)

 

2 more years passed.. still no update option, still checking out each commit. This is a 3 hour build for my project. No very good. I am better off building locally manually.

 

Another thread necro here.
Enabled UCB auto build on one of our projects yesterday and used $75 worth of bandwidth.
Disabled it this morning.

I'll happily pay Unity for storing the extra data. As it is now, we can't use the system.