top | item 35357851

GitHub Actions Incident 29.3

97 points| rethab | 3 years ago |githubstatus.com | reply

53 comments

order
[+] temp_account_32|3 years ago|reply
Funnily enough, GitLab is also melting down at the moment, with pipelines not running and pull requests not functioning:

https://status.gitlab.com/

[+] midasuni|3 years ago|reply
My on prem git lab has been fine with it’s pipelines, and given it’s impossible to have an on prem uptime higher than the cloud what you say can’t be true.
[+] kingds|3 years ago|reply
what's a pull request?
[+] rvz|3 years ago|reply
Once 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].

[0] https://news.ycombinator.com/item?id=35325850

[1] https://news.ycombinator.com/item?id=22867803

[+] carlmr|3 years ago|reply
Gittea is great but it doesn't replace GHA, only the rest of GitHub.
[+] chatmasta|3 years ago|reply
At 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.
[+] jacobsenscott|3 years ago|reply
Nobody's stock goes down when actions go down. Nobody's stock goes up when actions are working. But everyone's stock goes up when you have mass layoffs. Working as designed.
[+] riffic|3 years ago|reply
not sure what the SLA is on Actions but outages are a regular occurrence with these kinds of systems and are incredibly expensive to move to the next 9 of availability.

it's certainly a risk you'll need to evaluate when planning your desired build process.

[+] nimbius|3 years ago|reply
how is it in just five years microsoft has managed to pedal this once vibrant and bustling community of developers and creatives into a roaring dumpster fire of sketcky GPL breaking copilot AI and endless seemingly random outages.

https://www.githubstatus.com/history

github has had 55 outages in 3 months. thats nearly an outage every two days.

the last six months of 2022 had 74 outages. In many shops thats tangibly worse than what their local greybeard Linux admin maintains.

arguments against spinning up my own gitlab/gitea/jenkins/whatever in podman under systemd are starting to ring pretty hollow lately.

[+] _gabe_|3 years ago|reply
> how is it in just five years microsoft has managed to pedal this once vibrant and bustling community of developers and creatives into a roaring dumpster fire of sketcky GPL breaking copilot AI and endless seemingly random outages.

I mean Github Actions was released 5 years ago[0]. I imagine the infrastructure for actions is more susceptible to outages than the fairly simple features Github offered previously. It makes sense that the number of outages would increase with the additional complexity in the infrastructure.

[0]: https://resources.github.com/devops/tools/automation/actions...

[+] xxpor|3 years ago|reply
comments like these are what end up incentivizing companies to hide outages and report all green all the time
[+] deltaci|3 years ago|reply
this is already the third time github actions is down this week at wednesday morning
[+] mdaniel|3 years ago|reply
maybe they have a "no deploy on Friday" rule :-D
[+] web3-is-a-scam|3 years ago|reply
Github is so crappy now, it feels like something is always wrong with it. Thanks Microsoft.
[+] sithlord|3 years ago|reply
Wonder if these were managed by a defunct team from India?
[+] racl101|3 years ago|reply
Oh I get it.

[touches nose]

[+] riffic|3 years ago|reply
what is the "29.3" in the title supposed to represent? is that supposed to indicate a date of March 29th? I do not see a reference to this on the incident page itself.
[+] nurgasemetey|3 years ago|reply
It is because titles will be duplicated on search if 29.3 is not added
[+] gxt|3 years ago|reply
At what point are organisations going to ask themselves wether this is intentional or not. Your velocity is disrupted by a likely competitor. I'd move out.
[+] aaomidi|3 years ago|reply
I don’t have an opinion on it is or not but layoffs do have a significant impact on that and it’s generally something that’s pretty impossible to study.
[+] jacooper|3 years ago|reply
Or simply just self host actions?
[+] usrme|3 years ago|reply
Azure is also having somewhat widespread issues at the moment, so I'd venture to guess that these two are also linked.