|
hey theamk > TL/DR: this is "github runners as a service", and claimed build time improvement appears because they OpenFire gives more CPU/RAM resources that default Github runners. I guess a good idea if you rely on github's default runners... but if you are already using your own runners the benefit may or may not appear. For example hosting runners on EC2 is 2x cheaper, and gives you stuff like shared cache. I'm happy that you got the idea behind Open Fire "github runners as a service", yes you can run your runners in an EC2 instance, but on top of that, we're taking the burden of running those instances, having all the dependencies updated and working on building new features around the platform like analytics for your pipelines, local caches so the networking stop being a bottleneck for you runners, incremental building, instant checkout and more to come > Also, "just change 1 line of code" is a bit of exaggeration.. It is more like "sign up with Open Fire, enter your credit card, grant them access to all your git repos, change 1 line of code, don't forget to pay the bills". yeap, that is pretty much the idea, pretty neat for onboarding a new solution, right? |