Live data from Hacker News

GitHub was having issues

githubstatus.com

51–60 of 96 posts

Re: GitHub was having issues

#51
post #30

For people using GitHub Actions how often do these types of incidents impact your CI/CD?

All the time. It’s not even that reliable when it’s up. Total embarrassment for us when we have to explain to management. If I started again I’d probably use something standalone, light weight and 100% self hosted ie GoCD. I’d change the operating model to keep GitHub as a collaboration place but not have any dependencies on it for pipeline. We have other issues as well like the GitHub flow mod being inadequate for m…

From what I heard it was fine until Microsoft bought it and decided to bring over .net code (and people) from azure devops to replace a bunch of the pre-existing github actions stuff for some reason.

Re: GitHub was having issues

#52
post #7

Earlier quoted context omitted.

possibly Azure?

As far as I know GitHub doesn't use Azure at all, I think it's still hosted by Carpathia. https://github.com/holman/ama/issues/553

For github actions .net code and people were brought over from azure devops to replace existing stuff when MS bought it. At least so i've heard

Re: GitHub was having issues

#53
post #8

Maybe these are just a bunch of coincidences, but I have a feeling that GitHub is being poorly run recently. Apart from quite frequent uptime issues, it seems that Github Actions is pretty half-baked and they completely botched the migration of Dependabot (for example, take a look at this issue and especially, how it was handled: https://github.com/dependabot/dependabot-core/issues/3253 )

[deleted]

Re: GitHub was having issues

#55
post #30

Earlier quoted context omitted.

All the time. It’s not even that reliable when it’s up. Total embarrassment for us when we have to explain to management. If I started again I’d probably use something standalone, light weight and 100% self hosted ie GoCD. I’d change the operating model to keep GitHub as a collaboration place but not have any dependencies on it for pipeline. We have other issues as well like the GitHub flow mod being inadequate for m…

From what I heard it was fine until Microsoft bought it and decided to bring over .net code (and people) from azure devops to replace a bunch of the pre-existing github actions stuff for some reason.

What actions stuff existed before the acquisition?

Re: GitHub was having issues

#56
Things like this make me want to have more free time to start my own paid CI service. I can likely start from a few languages I know and take it from there.

I wonder how hard it is to write your own CI/CD though? Anybody has thoughts on this?

Re: GitHub was having issues

#57
post #42

For people using GitHub Actions how often do these types of incidents impact your CI/CD?

Very rarely, and (so far) not in any meaningful way. Having to wait a few hours for a CI process isn't a problem 99% of the time. Deploys are affected by issues on AWS and Azure far more often than GH in my experience. I'd probably change my mind if I ever get unlucky enough to need to deploy a critical hotfix at the same time GH is unavailable though.

If you're OK with waiting multiple hours for CI, I suppose these issues wouldn't affect you very much. Where I work we make relatively small PRs and deploy to production tens of times per day. The recent outages have been a nightmare for us.

Re: GitHub was having issues

#59

Earlier quoted context omitted.

As far as I know GitHub doesn't use Azure at all, I think it's still hosted by Carpathia. https://github.com/holman/ama/issues/553

For github actions .net code and people were brought over from azure devops to replace existing stuff when MS bought it. At least so i've heard

.NET code! That is a sure sign that nothing will work. /s

Re: GitHub was having issues

#60
post #15

Earlier quoted context omitted.

A shame they removed all their uptime graphs on the status page, since it's much harder to get a read on things now. However, scrolling back through the status page's history for the last year shows that there between 6 and 12 incidents every month, and it often hovers at the high end of that range. That has to be an utter misery for anyone who's on call.

> A shame they removed all their uptime graphs on the status page, since it's much harder to get a read on things now. I've started using that (uptime/performance/latency graphs being removed from status pages) as a signal to for when companies feel embarrassed over their quality of service but don't have enough interest/resources/profits to fix it.

> interest/resources/profits

It doesn't seem like Microsoft should have any of these issues. At most "interest", but even that should be a pretty easy sell for a service as massive as github.

Post reply on HN