Live data from Hacker News

Pricing Changes for GitHub Actions

resources.github.com

111–120 of 853 posts

Re: Pricing Changes for GitHub Actions

#113
Per-minute pricing for self-hosted runners seems like a very fast way for them to force everyone who actually is using self-hosted runners to migrate away.

I suspect we'll be doing that sometime in January or February.

I guess forgejo is the easiest migration path? https://forgejo.org/

Re: Pricing Changes for GitHub Actions

#114

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?

On ZeroFS [0] I am doing around 80 000 minutes a month.

A lot of it is wasted in build time though, due to a lack of appropriate caching facilities with GitHub actions.

[0] https://github.com/Barre/ZeroFS/tree/main/.github/workflows

Re: Pricing Changes for GitHub Actions

#115

Microsoft has started raising prices on many of their products. I suppose they decided that their current customers need to pay the increased CapEx for AI;) New motto - AI pay for it whether you use it or not.

No such thing as free parking

No but there is validated parking for customers of other services.

This is going to be the downfall of GA

Re: Pricing Changes for GitHub Actions

#116

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.

I think you significantly underestimate the number of CI minutes people are using in practice.

(Which, yes, has implications for energy use/climate change too for sure).

It doesn't look like i currently have access to the usage data on any of the lots-of-runners-lots-of-PRs projects I currently work on (which are still probably way less than some large companies).

Re: Pricing Changes for GitHub Actions

#117
post #10
post #5

That makes me genuinely curious about the internal hosted vs. self-hosted usage ratio they're seeing. I'd have guessed the bulk of the cost/volume was on hosted, but clearly that can't be the case

Anecdotally I've seen it get a lot more common to use third-party managed runners (e.g. Blacksmith) for anyone that needs slightly beefier machines and/or a caching system that actually works.

Yeah, we migrated to self hosted actions runnrers on hetzner 2 years ago, the speed improvement was massive

Re: Pricing Changes for GitHub Actions

#118

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.

Doesn't this depend a lot on how long your actions run? Like, you may have already invested in your own hardware (maybe because your actions use a lot of resources and it's cheaper) and now you have to pay per-minute of action runtime for the API that does the bookkeeping?

Re: Pricing Changes for GitHub Actions

#119

Earlier quoted context omitted.

I had the same question — I understand that the Actions control plane has costs on self-hosted runners that GitHub would like to recoup, but those costs are fixed per-job. Charging by the minute for the user’s own resources gives the impression that GitHub is actually trying to disincentivize third-party runners.

Might be an estimation of logs storage/bandwidth.

That's generous, but doesn't seem consistent with how Microsoft does business. Also, if that's the case why does self-hosted cost the same as the lowest hosted tier?
Post reply on HN