GitHub Outage Currently Ongoing – Issues, PRs, Notifications
githubstatus.com
GitHub Outage Currently Ongoing – Issues, PRs, Notifications
1–10 of 106 posts
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#2Events like this make me realize how much I rely on my CI/CD pipeline for working on new features, deploying etc. I am often too lazy to run E2E tests on my machine if I know that on CI it will take only a few minutes to be done.
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#3Seems like github will soon become part of office 356 /s
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#4Justyna yesterday I was complaining about GitHub monoculture in the context of Atlassian sunsetting Mercurial.
Outages like this are normal, but the problem is lack of good competitors.
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#5Justyna yesterday I was complaining about GitHub monoculture in the context of Atlassian sunsetting Mercurial. Outages like this are normal, but the problem is lack of good competitors.
There are quite a decent list of competitors, all of which have similar or sometimes better offerings. There are also plenty of fully free and open source solutions, should you want to do things yourself.
The Github monopoly is driven by its users.
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#6Justyna yesterday I was complaining about GitHub monoculture in the context of Atlassian sunsetting Mercurial. Outages like this are normal, but the problem is lack of good competitors.
I think you're right about a general move towards a Git monoculture (as opposed to a GitHub one), but there are dozens of great Git repo hosting/collaboration companies - GitLab, Bitbucket & SourceForge to name a few of the bigger ones
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#7Alright, cue the usual:
Monoculture bad
Microsoft bad
Git is distributed but all the things around it that we really need aren't
You can set up git to push to multiple remotes automatically
Nobody is actually using git in distributed mode
Did I forget anything?
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#8Alright, cue the usual: Monoculture bad Microsoft bad Git is distributed but all the things around it that we really need aren't You can set up git to push to multiple remotes automatically Nobody is actually using git in distributed mode Did I forget anything?
The usual fluff about migrating away to Gitlab?
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#9Justyna yesterday I was complaining about GitHub monoculture in the context of Atlassian sunsetting Mercurial. Outages like this are normal, but the problem is lack of good competitors.
The problem is bad design and/or integration of components. VMS clusters over leased lines went years without outages. Record was 17 years at a rail yard. They also did rolling upgrades across both different OS versions and CPU architectures. The methods are public if any competitors want to match or exceed them:
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na...
These modern cloud services using Linux ecosystem are doing rolling outages instead. I'm amazed people keep making them dependencies. Maybe their local systems using similar technology went down more often. Maybe this is an improvement. I'd still put mine on an OpenBSD or OpenVMS cluster if it was business-critical with lots of money on the line. I want it staying up, up, up. :)
Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications
#10Git is designed as distributed VCS, so an outage of a centralized server should not matter too much. So far, the theory. Using Github excessively is the way back to centralization, nowadays handing control over to Microsoft. Everybody who is concerned (probably not too much) should have a look into alternatives.