[perbu]

The reason this makes sense, at least for Github, is because the only valid reason to run your own action runners is compliance. And if you are doing it for compliance, price doesn't really matter. You don't really have a choice.

If you've been running your runners on your own infra for cost reasons, you're not really that interesting to the Github business.

[zamalek]

Github runners are slow. We're using WarpBuild and they are still cheaper per-minute, even with all the changes Github has made. Then there's the fact that the machines are faster, so we are using fewer minutes.

There are multiple competitors in this space. If you are (or were) paying for Github runners for any reason, you really shouldn't be.

[suryao]

Thanks for the WarpBuild love!

Performance is the primary lever to pay less $0.002/min self hosting tax and we strive to provide the best performance runners.

[Sytten]

We also use WarpBuild and very happy with the performance gain. This changes nothing except maybe it should signal to WarpBuild to start supporting other providers than Github. We are clearly entering the enshitiffication phase of Github.

[CafeRacer]

I needed arm64 workers, because x86 would take ~25 minutes to do a build.

[llimllib]

if it's useful, they do actually have arm workers now for linux and mac: https://github.com/actions/runner-images/tree/main?tab=readm...

[normie3000]

TIL amd64 is also called x86-64.

[justincormack]

They have these now.

[esseph]

Performance and data locality.

You can throw tons of cores and ram locally at problems without any licensing costs.

Your data may be local, makes sense to work with it locally.

[briHass]

Maybe if everything you use is public-cloud-deployed.

Self-hosted runners help bridge the gap with on-prem servers, since you can pop a runner VM inside your infra and give it the connectivity/permissions to do deployments.

This announcement pisses me off, because it's not something related to abuse/recouping cost, since they could impose limits on free plans or whatever.

This will definitely influence me to ensure all builds/deployments are fully bash/powershell scripted without GH Action-specific steps. Actions are a bit of a dumpster fire anyway, so maybe I'll just go back to TeamCity like I used before Actions.

[saagarjha]

Not just compliance, we run CI against machines that they don’t offer, like those with big GPUs.