RE: hachyderm.io/@fasterthanlime/1

Why in the world are Github introducing a per-minute charge for running jobs on my own servers? To disincentivise using private servers.

That's not their claim; rather, they assert it's because the new infrastructure (which they say is more efficient!) newly needs to be charged for as a separate line item to keep up with demand.

Except using one of their own linux_thin VM instances for actually running the job itself incurs *zero* additional cost…?

I call bullshit.

docs.github.com/en/billing/ref

(This may result in lots of orgs looking to switch to webhook-triggered CI/CD builds rather than using Github's Actions infrastructure.)

On the one hand, maybe the marginal cost of running thin Linux guests really is effectively zero when you're operating at the scale of Github? Or they want to subsidise such use by users running larger runners to avoid shocks to the system.

On the other hand, Github putting taxes on something that's long been free-at-the-point-of-use when you might reasonably expect it to be factored into baseline costs, such as hosting their own DNS or network bandwidth, does sound like the act of a distressed org? Which, if you're reliant on it, is worrying.

Especially given the short notice.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.