GitHub Actions Incident 29.3
githubstatus.com
GitHub Actions Incident 29.3
1–10 of 56 posts
Re: GitHub Actions Incident 29.3
#2this is already the third time github actions is down this week at wednesday morning
Re: GitHub Actions Incident 29.3
#3[deleted]
Re: GitHub Actions Incident 29.3
#4Funnily enough, GitLab is also melting down at the moment, with pipelines not running and pull requests not functioning:
Re: GitHub Actions Incident 29.3
#5Once again, just two days ago [0], the whole of GitHub went down, after the RSA key leakage and the certificate key expiry on its user facing site.
It is also apparent that GitHub Actions has chronically been struggling to operate normally for at least once a month for years.
There is no question that GitHub has been more unreliable than if you were to use a self-hosted GitLab or Gittea instance yourself as I said before [1].
Re: GitHub Actions Incident 29.3
#6this is already the third time github actions is down this week at wednesday morning
maybe they have a "no deploy on Friday" rule :-D
Re: GitHub Actions Incident 29.3
#7this is already the third time github actions is down this week at wednesday morning
maybe they have a "no deploy on Friday" rule :-D
I sure hope not, GitHub is supposed to be matured infrastructure at this point, where most if not all changes going into production should be very well tested and nothing that multiple people haven't verified as being correct should end up being deployed and released.
Besides, Microsoft surely has 24/7 watch of their infrastructure, even on weekends, it's a huge company.
Re: GitHub Actions Incident 29.3
#8Earlier quoted context omitted.
maybe they have a "no deploy on Friday" rule :-D
I sure hope not, GitHub is supposed to be matured infrastructure at this point, where most if not all changes going into production should be very well tested and nothing that multiple people haven't verified as being correct should end up being deployed and released. Besides, Microsoft surely has 24/7 watch of their infrastructure, even on weekends, it's a huge company.
Bugs are a function of change, not a function of maturity.
Just because they can have people come in on weekends to fix things doesn’t mean they like doing that.
I know many “mature” software platforms that do not deploy on Fridays or off hours at all
Re: GitHub Actions Incident 29.3
#9At least we don't need to scroll too far back in our comment history to copy/paste our arguments from the thread two days ago.
Re: GitHub Actions Incident 29.3
#10Earlier quoted context omitted.
maybe they have a "no deploy on Friday" rule :-D
I sure hope not, GitHub is supposed to be matured infrastructure at this point, where most if not all changes going into production should be very well tested and nothing that multiple people haven't verified as being correct should end up being deployed and released. Besides, Microsoft surely has 24/7 watch of their infrastructure, even on weekends, it's a huge company.
> Besides, Microsoft surely has 24/7 watch of their infrastructure, even on weekends
"watching" with a dedicated team vs "waking up everyone in engg because things are on fire" are two very different things.
Besides, size doesn't work that way. The larger the organization and the more complex the product is, the higher the chance some unexpected interaction will occur. There are processes and automation that can mitigate this, but one can never be completely certain.
Not even the aviation industry has mastered that.