I have the opposite response to Patico’s unfortunately…at this point, waiting for a Cloud build to be queued and processed is too much of an opportunity cost to consider it usable.
I can’t give reliable stats because the interface doesn’t display a timestamp for when the build was queued, but I can state that over the last 24 hours, my builds have been in the “Pending” in excess of an hour to an hour and a half per build…and then take 20 minutes minimum (and that’s being generous), with an average of > 45 minutes more likely…to build something that takes roughly a minute and a half on a desktop.
My project has to synchronize server and client builds, and when a new feature rolls out on the server, the last client build is obsoleted so the testers don’t wind up wasting time with cross-build incompatibilities. It logically follows that since they can’t test, all testing stops for 1-3 hours every time a new build is rolled out, and the lockout is simply due to the cloud build process.
I realize that projects can 'buy" priority (dedicated build server)–but one of the considerations for going with a Pro license was the addition of free cloud build services for the first year…yet since these services are so slow as to be unusable by a reasonably sized team (1 dev, 1 producer, 3-5 testers), I’m stuck with either paying for a service that was supposed to be a free incentive (by renting dedicated server for the build), or having to build my own after all.
I understand that marketing gets ahead of services sometimes–it happens. But right now, offering “free cloud build services for 1 year” is basically misleading your customers.
Icing on the cake: after waiting for over an hour for the build to kick off, it comes back with:
Summary: 1 warnings, 2 errors:
ERROR: Error cloning remote repo ‘origin’ : Could not clone git@github.com:.git
ERROR: Could not clone repository
Caused by: java.io.IOException: Could not clone
–this is on a repo where nothing has changed in a month and a half except for new commits.
