My desktop machine can fully rebuild the game in a few minutes. Azure takes 20-30 minutes. I'm sure many of these cloud services are using way over worked VMs. I'll deal with it because I don't want to set up and maintain my own machines for building. I have a game to make and CI build machines isn't where I want to spend any effort.
@grumpygamer this is an interesting idea and (as presented anyway) economical. Building on scalable "serverless" nodes where you only pay for the non-idle miliseconds. https://blog.nelhage.com/post/building-llvm-in-90s/
@grumpygamer I was really surprised, when there was no option to just select to pay for more capable build agents. Everywhere else it feels like Azure happily takes more money in exchange for more performance, and I don't get why I would need to prepare a VM myself, if I am unhappy with building on retired toasters as build agents…
@TheConstructor @grumpygamer when the continuous integration book said “the build should take 10 minutes, max” we were rocking Pentium IIs. It’s ridiculous all of it.
@grumpygamer the idea of cloud is running everything in parallel on VMs. So start a job for each platform and not one job building all platforms.
@grumpygamer so langsam wird klar, dass „Cloud“ nicht immer die Lösung ist.
Vieles macht man doch besser selbst.
@grumpygamer or them be like “virtual private server with 6 cores!!!11” but the cores are from 10 year old Haswell Xeons…
@grumpygamer Azure’s Mac build machines have been hot garbage for years.
@grumpygamer Is it possible, that you always have a clean build for the CI builds and locally you only compile files that actually changed. If this is the case it could be useful to look into how to setup caches in your CI pipeline.
@hwmrocker I don't want that. I want a clean build.