logoalt Hacker News

embedding-shapelast Thursday at 10:24 AM2 repliesview on HN

I wonder if Microsoft will ever get that asking users before making changes can help them avoid looking bad in public.

Maybe half of all clients I work with use GitHub Actions for CI (the rest basically all use Jenkins), most of those using Actions use self-hosted runners for performance and security reasons, almost all of them reached out to me asking how difficult it would be to move away from GitHub Actions yet continue using GitHub.

Do you think these companies now suddenly stop wanting to move away from GitHub Actions because Microsoft suddenly changed their mind? I don't think so, probably less priority, but it will happen, because now the cat is out of the bag.

If they'd just do user research before announcing changes and not use announcements as "testing the waters", I'm sure they'd see a lot less churn. But I guess some number counting team somewhere in Microsoft figured out they'd make more money by charging people to run software on their own hardware, so maybe I'm just dreaming.


Replies

Xylakantlast Thursday at 11:19 AM

Fun thing is that almost every other CI as a service provider charges you in some shape or form for self hosted runners. CircleCI limits the number of self-hosted Job Running in parallel based on your plan and charges a fixed base fee per seat.

So moving away from GHA will not make self-hosted runners free, they’ll move into a different pricing structure that may or may not be beneficial.

And I think charging for self-hosted runners is actually fine. They’re not free for the provider either - log aggregation, caching of artifacts, runner scheduling, implementing the runner software etc are non-trivial problems for any larger CI system.

So I’m actually fine with the proposed change since it also gives me the power as a customer to say “hey, I’m paying for this, fix it.”

show 8 replies
markus_zhanglast Thursday at 2:12 PM

MSFT used to be extremely good about that in the 90s. From the book Showstoppers: MSFT sent not one, but three batches of NT 3.1 beta to external developers before the final release.

The idea nowadays is iterate fast and break things (as long as it’s not your wallet or your leg).