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.
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].
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.
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.
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.
> 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.
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.
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.
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.
[+] [-] temp_account_32|3 years ago|reply
https://status.gitlab.com/
[+] [-] bencevans|3 years ago|reply
1: https://gitlab.com/gitlab-org/gitlab/-/issues/402616 2: https://github.com/microsoft/vcpkg/issues/30481
[+] [-] midasuni|3 years ago|reply
[+] [-] kingds|3 years ago|reply
[+] [-] rvz|3 years ago|reply
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
[+] [-] chatmasta|3 years ago|reply
[+] [-] jacobsenscott|3 years ago|reply
[+] [-] riffic|3 years ago|reply
it's certainly a risk you'll need to evaluate when planning your desired build process.
[+] [-] nimbius|3 years ago|reply
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
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
[+] [-] deltaci|3 years ago|reply
[+] [-] mdaniel|3 years ago|reply
[+] [-] web3-is-a-scam|3 years ago|reply
[+] [-] sithlord|3 years ago|reply
[+] [-] racl101|3 years ago|reply
[touches nose]
[+] [-] riffic|3 years ago|reply
[+] [-] nurgasemetey|3 years ago|reply
[+] [-] gxt|3 years ago|reply
[+] [-] aaomidi|3 years ago|reply
[+] [-] jacooper|3 years ago|reply
[+] [-] usrme|3 years ago|reply
[+] [-] esotericimpl|3 years ago|reply
[deleted]
[+] [-] unknown|3 years ago|reply
[deleted]