4 ms·
To offer a data point (not a tribalist argument): GitHub Actions being down this often is still less expensive than the cost of switching everything somewhere
by Waterluvian 3mo ago
To offer a data point (not a tribalist argument): GitHub Actions being down this often is still less expensive than the cost of switching everything somewhere else. Would rather have my team walk away from the PRs and do other tasks than have engineering effort, meetings, design pages, scheduling, etc. for switching over.
This is annoying and I'm here because it's down. But it would have to be far worse to come close to actually being worth changing.
- SoftTalker 3mo agoA case study in vendor lock-in.
- Waterluvian 3mo agoPretty much, eh? If I could right now: 1. go sign-up elsewhere 2. Log into GitHub and point Actions to that new host 3. All my actions files immediately worked without question I'd probably give it a spin and make a wiki page explaining how to swap back and forth. No meetings. No design issues. No scheduling. Just a flip switch on who to pay for computers.
- inigyou 3mo agoThat's why GHA makes you write these weird ridiculous YAML files instead of shell scripts.
- random_savv 3mo agoFor what it's worth, we switched some of our actions to a self-hosted Woodpecker instance, and although there were a few kinks to iron out, it works better overall (for example, because of better caching on that single instance, our docker images build faster).
- deleted 3mo ago[deleted]
- sleepybrett 3mo agoWe've started writing some new workflows against argo-workflows for the last like 9months or so. Especially for use cases where the actions are like self-service type automation. I think people were so excited to move away from jenkins to something 'managed' just because of how much a dinosaur jenkins is and how much a pain in the ass it is to upgrade it... but now we are seeing how managed can bite you in the ass if the manager is incompetent.
- macintux 3mo agoI’m intensely grateful that despite rumblings, the company I contract to hasn’t switched from self-hosted Jenkins to GHA. Hopefully the steady drumbeat of failure will keep it that way.
- Waterluvian 3mo agoIf that’s how you feel, make sure you share that feedback with the deciders!
- monkaiju 2mo agoIn my experience moving from GH to Forgejo was trivial, largely because the actions are mostly compatible and importing the repos can be automated. The amount of time it took was definitely less than the 5-8 hours of downtime that GHA had yesterday.