![]() I realise no-one wants to hear excuses, everyone is here for updates so. As with most Apple upgrades, new hardware and software upgrades are required, both of which have their own level of risk which deserves the highest level of acceptance testing. There are multiple reasons for the delay in releasing new technologies on Cloud Build, the main reason being to ensure the stability of the service for all users. We do understand that the interim period between Apple's release of Xcode and when it becomes available on Unity Cloud Build can be very frustrating when everyone has their own deadlines to meet. The least of these requirements being able to ship products day-and-date with the release of new tools/operating system revisions.įirstly, thanks for everyone's continued patience with the service. I realize that the scale and coordination that the servers/service are represent an incredible challenge to maintain and support, but if Unity wants to prop up its engine with additional services: studios should be able to rely on those for their business cases. The least of these requirements being able to ship products day-and-date with the release of new tools/operating system Checking in a couple weeks later, is there an ETA yet? It's been over three weeks since Xcode 11 has been released. ![]() ![]() Moreover, this seems to be the norm for UCB with little to no acknowledgement of planned improvement on this front. This often means that for the projects that we rely on Cloud Build for, our efficiency gets killed around new Xcode releases since we're switching to local, manual builds to run our test suites instead of the daily builds we get with Cloud Build. It's incredibly frustrating to not have these tools available to us at this point, and not an excuse that clients are willing to put up with. ![]() Checking in a couple weeks later, is there an ETA yet? It's been over three weeks since Xcode 11 has been released.Īlso, just to provide some feedback about this, having Cloud Build consistently 3+ weeks behind the actual release of the products that it uses is forcing our team to look into running our own Jenkins server to manage our own build and release process. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |