Earlier quoted context omitted.
Enterprise says I have to use this unreliable garbage.
It's definitely no less reliable than GitLab, where a good 300GB of database data got deleted in production by accident...
GitHub incident: ongoing issues with Actions, Issues and other Git operations
71–80 of 130 posts
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#72Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#73Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#74Does GitHub provide uptime stats? Seems very unreliable recently.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#75Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#76Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#77Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#78Does GitHub provide uptime stats? Seems very unreliable recently.
About 10 years ago someone said we should move to self hosting because bitbucket who we used were unreliable. I looked at the status page and say 2 hours of downtime over 3-months, while we have 3-4 days of downtime on our self hosted jenkins during the same time. I always think of that when I see people complain about services being unreliable. Often we see one or two problems in short span and forget about the mont…
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#79I debugged for one min at 11:59 trying to push, and then my eat-lunch notification came in at 12:00 and I opened hackernews with a tuna sandwich and this is super helpful because it means I wont need to debug it locally for 10 mins before figuring out Github is down. Edit - Just want to clarify when I say "opened hackernews with a tuna sandwich" I want to clear up that I did indeed full on mash the keyboard letters w…
This is why I don't touch other people's keyboards.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#80Earlier quoted context omitted.
You can self-host GitLab and have few, if any, incidents that get resolved very quickly. Worked for a company that had no incidents that I observed in ~3 years, now work at a company that had ~2 incidents in 1.5 years.
We have a self-hosted Premium instance and have 30min of downtime _every day_ while the database is frozen and backed up. We've been told that it's a known issue being discussed with GitLab but that could just be CYA. But in any case, it's the "at scale, while changing" that tends to cause problems. Perhaps this is a continuing argument for self-hosting, especially if you don't have to expose the instance publicly. B…
I'm confused. You can do zero-downtime backups and replication of databases. I don't know what your company / Gitlab are doing but it seems wrong.