Live data from Hacker News

Pricing Changes for GitHub Actions

resources.github.com

91–100 of 853 posts

Re: Pricing Changes for GitHub Actions

#91
post #2

> We are introducing a $0.002 per-minute Actions cloud platform charge for all Actions workflows across GitHub-hosted and self-hosted runners. Charging for self-hosted runners is an interesting choice. That's the same cost as their smallest hosted runners [1] [1] - https://docs.github.com/en/billing/reference/actions-runner-...

It's because there are easy-to-use third party runners that cost around 3-10x less than the GitHub ones. This is aimed squarely at them.

https://github.com/neysofu/awesome-github-actions-runners

Re: Pricing Changes for GitHub Actions

#92
post #2

> We are introducing a $0.002 per-minute Actions cloud platform charge for all Actions workflows across GitHub-hosted and self-hosted runners. Charging for self-hosted runners is an interesting choice. That's the same cost as their smallest hosted runners [1] [1] - https://docs.github.com/en/billing/reference/actions-runner-...

it'd be great if they can couple this with an SLA for GitHub actions so we won't have to end up paying as much.. (ofc, that'd only mean they stop updating the status page, so eh)

For what it's worth, they already fail to update the status page. We had an "outage" just this morning where jobs were waiting 10+ minutes for an available runner -- resolved after half an hour or so but nothing was ever posted

https://downdetector.com/status/github/

Re: Pricing Changes for GitHub Actions

#94
Everyone in this thread has gone absolutely insane. $5/month gets you 41 fucking _hours_ of continuous operation. If you're not utterly abusing the platform, this falls extremely below the threshold of caring. And if not, what the fuck are you even doing with all those hours? The new per-minute charge is less than one millisecond of engineer labor cost.

Re: Pricing Changes for GitHub Actions

#95

Introducing a separate charge specifically targeting those of your customers who choose to self-host your hilariously fragile infrastructure is certainly a choice.. And one I assume is in no way tied to adoption/usage-based KPIs. Of course, if you can just fence in your competition and charge admission, it'd be silly to invest time in building a superior product.

They still host all artefacts and logs for these self-hosted runs. Probably costs them a fair bit

They already charge for this separately (at least storage). Some compute cost may be justified but you'd wish that this change would come with some commitment of fixing bugs (many open for years) in their CI platform -- as opposed to investing all their resources in a (mostly inferior) LLM agent (copilot).

Re: Pricing Changes for GitHub Actions

#97
a per-job cost instead of per-minute cost for non-compute "control plane" for CI would have made more sense and seemed more reasonable to me -- but don't really know if customers would have liked it better/worse or paid more/less under it.

(I work exclusively on public repo open source at the moment, and get Github actions for free).

Re: Pricing Changes for GitHub Actions

#98

Tangled has a nix based workflow engine that looks very similar, if you are into nix and self-hosting runners https://tangled.org/tangled.org/core/blob/master/docs/spindl... (no affiliation) --- Blog post about Tangled's CI: https://blog.tangled.org/ci

Useless for Mac or Windows presumably.

Re: Pricing Changes for GitHub Actions

#100

Earlier quoted context omitted.

This is absolutely bananas; for my own CI workflow I'll have to pay $140+/month now just to run my own hardware.

I'm curious, what are you doing that has over 1000 hours a month of action runtime?

I run a local Valhalla build cluster to power the https://sidecar.clutch.engineering routing engine. The cluster runs daily and takes a significant amount of wall-clock time to build the entire planet. That's about 50% of my CI time; the other 50% is presubmits + App Store builds for Sidecar + CANStudio / ELMCheck.

Using GitHub actions to coordinate the Valhalla builds was a nice-to-have, but this is a deal-breaker for my pull request workflows.

Post reply on HN