If you rely on Actions and want proper monitoring to alert you of these kinds of things, Cronitor has pretty a nifty monitoring plugin (which, itself, is an action, naturally)
GitHub Actions Down / Degraded
31–40 of 48 posts
Re: GitHub Actions Down / Degraded
#32Funny how my troubleshooting mind works - I assumed I had borked the config, then assumed they had introduced a bug, then found the real reason is an outage.
I just remember my professor drilling down in my head that if my code doesn't build, 99%+ chance is that it isn't a bug in the compiler.
We are taught early on that if something doesn't work, it is because something is wrong in our code.
Re: GitHub Actions Down / Degraded
#33Again? Last time an incident like that happened was Packages which was less than 24 hours ago. [0] Before that weeks ago [1] At this point, it is clear that GitHub is essentially falling apart and is becoming extremely unreliable. It's not too late to join the serious projects like Blender, ReactOS, RedoxOS, etc who are happily self hosting and are not going all in on GitHub. I posit that they even have better uptime…
> happily self hosting That can also be a nightmare. Do you want git hosting, CI/CD, etc. to be among your core competencies? Because that's what this entails. You need a full team to staff it and be on call. I guarantee you that those who self host will have just as many breakdowns. Five nines is hard, especially when it's not your main job.
It isn't that hard to have a build server and run a shell script on a timer.
Re: GitHub Actions Down / Degraded
#34Earlier quoted context omitted.
> happily self hosting That can also be a nightmare. Do you want git hosting, CI/CD, etc. to be among your core competencies? Because that's what this entails. You need a full team to staff it and be on call. I guarantee you that those who self host will have just as many breakdowns. Five nines is hard, especially when it's not your main job.
It isn't that hard to have a build server and run a shell script on a timer.
Yeah, and don't forget to run the shell script in screen as well so you can detach it /s
Re: GitHub Actions Down / Degraded
#35Re: GitHub Actions Down / Degraded
#36I keep threatening to move us to enterprise but the temperature never quite gets high enough to push me over the actual threshold. I would be curious if anyone else on HN is responsible for running a GH Enterprise instance and whether or not the extra liability is worth it.
There's pretty severe scaling issues with GH Enterprise for large codebases, but for small shops it's probably fine.
Re: GitHub Actions Down / Degraded
#37Again? Last time an incident like that happened was Packages which was less than 24 hours ago. [0] Before that weeks ago [1] At this point, it is clear that GitHub is essentially falling apart and is becoming extremely unreliable. It's not too late to join the serious projects like Blender, ReactOS, RedoxOS, etc who are happily self hosting and are not going all in on GitHub. I posit that they even have better uptime…
why always repeatedly write the same comment about not going “all in on github” in these threads? what is goal of writing this hundred+ times?
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
i dislike github quite alot but this does not achieve anything. no one else is saying to go all in on github so what is this even reply to?
Re: GitHub Actions Down / Degraded
#38I keep threatening to move us to enterprise but the temperature never quite gets high enough to push me over the actual threshold. I would be curious if anyone else on HN is responsible for running a GH Enterprise instance and whether or not the extra liability is worth it.
Just be forewarned that GHE is not at feature parity with .com; back before I jumped ship to GitLab we were waiting forever for some of the most basic features to be backported, and that's not even getting into the mess that is "tools which claim to work with GitHub but haha have github.com hardcoded everywhere
The sibling comment about needing to use a partner may speak to this, but unlike GitLab GHE is also not `docker run ...` and tada, so you're right to be wary of the pain
Re: GitHub Actions Down / Degraded
#39I know I'm gonna get flamed for this after the responses on the Gitlab pricing post this morning but I'm gonna do it anyway.
Just sayin... Bitbucket pipelines reliability over the last months has been looking pretty sweet compared to GH Actions...
Bitbucket: https://bitbucket.status.atlassian.com/history?page=1&filter...
Re: GitHub Actions Down / Degraded
#40I keep threatening to move us to enterprise but the temperature never quite gets high enough to push me over the actual threshold. I would be curious if anyone else on HN is responsible for running a GH Enterprise instance and whether or not the extra liability is worth it.
We've been running GitHub Enterprise Server (first on-prem, now in a Cloud VM) for many years. Size: low thousands of repos, less than a terabyte of total data.
Pros: Not affected by GitHub.com downtime; stability has generally been good for us; you have full control over the org and user names on the instance (instead of having to pick globally-unique ones on github.com); can sync licenses between GHES and github.com if you want to use some private repos on github.com; can raise your API rate limit as high as you want; probably cheaper to provide your own storage.
Cons: New features from github.com can take months (or longer) to be released to GHES; many third-party integrations only work with github.com not GHES; if something goes down, it's now your fault; Actions requires bring-your-own self-hosted runners; autoscaling your self-hosted runners is non-trivial.
The last point is probably the biggest negative for us. We're trying to use GitHub Actions more, but I don't really want to have to manage a pool of autoscaling runners. (I'm doing it, though.) If GitHub provided an add-on service to connect GitHub-managed cloud runners to GHES, I'd use it. (Needing to always keep code private and on-premises is not a requirement for us.)