They have the "work" of uploading the game via the second webappīecause of these concerns I wanted to automate this process.The developers all build the Games on their dev Machines which "locks" the PC from any other use / further development.This upload happens through a separate Page I set up for the various Developers we have in the Team. I am currently showing those Games via WebGL on a Website that requests the data files (wasm, data etc.) from an Azure Blob Storage where I upload the files to. More or less those are multiple "minigames" that all have the same foundation. In the cloud I can say ‘run the build on 6 servers’ and be done with it.Im a currently working on mutliple Unity projects that share quite a lot of prefabs, scripts etc. If you need speed, you need to buy more hardware, install it, maintain it etc. If the game grows it will have longer build times. And a build server in the cloud opens up the possibility for scaling etc. In the end it could be cheaper than having my own hardware for building. If I dont need to maintain a build server, I have time to work on the game. I dont want to maintain my webserver: handling log files, keeping OS up to date, keeping web server software up to date, worrying about hardware replacement when its too old or is broken etc. Nothing easier than dumping the stuff at Azure/Amazon/Google and let them handle everything. Same reason IAAS/PAAS/SAAS/etc exists these days.
Well, for a small team it might be interesting. Also, does it have to be Epic? Could be another company providing the service. No need to take resources out of the engine development team. If the service is paid, they can hire people for this service. If you can’t even afford one dedicated machine to handle builds, I doubt your project is big/complex enough to really be in need of such services There is something wrong with that, because it means Epic needs to take some of its resources out of the engine development team, and assign them to handling services like cloud build.
0 kommentar(er)
