Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitlab was down

status.gitlab.com

Post reply on HN
Print view View original

81–90 of 140 posts

Re: Gitlab was down

#81

Post by jlengrand »

kungtotte wrote: post #73
jlengrand wrote: post #66

I used to be a total Gitlab fanboy. I was going to Sid's meetups back in Utrecht 6 years ago, and he's a model of mine to this time. I would have done anything to stay on the platform, for at home and the office and setup gitlab instances in two different offices. Since somewhere last year, I moved back to Github primarily, and I'm sad to hear that my company is likely to make the same choice soon.The only reason is…

Whenever GitHub is down you see comments saying much the same thing only with the names reversed. The thing that strikes me each time is how fragile everyone's setup is if GitHub/lab is a single point of failure for them... At least gitlab let's you self host, which would let you run backups on offsite hosting meaning zero downtime.

Agreed, nobody's perfect.

My experience with github is much better though on average. Haven't had a single bad experience personally the past year for my personal stuff. Not once. Github does only one thing, the CI is usually somewhere else so there have less reasons to fail as well... It might be comparing apples and oranges.

We use Gitlab at the office and it is constantly slow. Might be our setup I agree, but in the end it also tarnishes the brand to me.

All in all, my general experience is that speed and stability has degraded over the past years, in favor of the 'whole in one devops pipeline'. Github stayed focus on its core market.

Re: Gitlab was down

#82

Post by stevekemp »

Dayshine wrote: post #49
greens231 wrote: post #46

Originally joined gitlab for their free private repos but with the recent downtime/sluggishness, i have jumped over to github (now that they offer free private repos too)

Gitlab is still the only viable choice for non-commercial groups who want private repos though, the 3 private members and no ability to have mixtures of public/private repos in organisations on Github is very limiting.

Bitbucket? (Even though their availability is terrible too.)

Re: Gitlab was down

#83

Post by ramchip »

kungtotte wrote: post #73
jlengrand wrote: post #66

I used to be a total Gitlab fanboy. I was going to Sid's meetups back in Utrecht 6 years ago, and he's a model of mine to this time. I would have done anything to stay on the platform, for at home and the office and setup gitlab instances in two different offices. Since somewhere last year, I moved back to Github primarily, and I'm sad to hear that my company is likely to make the same choice soon.The only reason is…

Whenever GitHub is down you see comments saying much the same thing only with the names reversed. The thing that strikes me each time is how fragile everyone's setup is if GitHub/lab is a single point of failure for them... At least gitlab let's you self host, which would let you run backups on offsite hosting meaning zero downtime.

Github also supports self-hosting.

Re: Gitlab was down

#84

Post by mikekchar »

jlengrand wrote: post #81
kungtotte wrote: post #73

Earlier quoted context omitted.

Whenever GitHub is down you see comments saying much the same thing only with the names reversed. The thing that strikes me each time is how fragile everyone's setup is if GitHub/lab is a single point of failure for them... At least gitlab let's you self host, which would let you run backups on offsite hosting meaning zero downtime.

Agreed, nobody's perfect. My experience with github is much better though on average. Haven't had a single bad experience personally the past year for my personal stuff. Not once. Github does only one thing, the CI is usually somewhere else so there have less reasons to fail as well... It might be comparing apples and oranges. We use Gitlab at the office and it is constantly slow. Might be our setup I agree, but in t…

To be fair, Over the last 5 years, I've been hit by several Github outages and never been hit with a Gitlab outage. The reason? I don't use Gitlab during my working day. Similarly with this one, I wasn't doing anything on Gitlab when it went down.

Re: Gitlab was down

#85

Post by dijit »

tyingq wrote: post #55
softwarelimits wrote: post #43

Earlier quoted context omitted.

How do you know that they do not hire "any people with ops experence"? Do you have insight? Is there any public evidence for this or anything you could publish yourself to add some substance to your words? It would be great if you understand that just saying something is not enough on the internet.

As recently as October 2017, they had exactly one database person. So I can imagine quite a lot of work and hiring needed to scale up a solid ops practice. "Until very recently I was the only database specialist which meant I had a lot of work on my plate." https://about.gitlab.com/blog/2017/10/02/scaling-the-gitlab-...

Almost to prove my point Yorick self-identifies as a "Ruby/Rust Developer" https://railsisrael2016.events.co.il/people/2644-yorick-pete...

Obviously this doesn't preclude operations or systems knowledge but again, it's at least telling of the mindset.

Re: Gitlab was down

#86

Post by jlengrand »

mikekchar wrote: post #84
jlengrand wrote: post #81

Earlier quoted context omitted.

Agreed, nobody's perfect. My experience with github is much better though on average. Haven't had a single bad experience personally the past year for my personal stuff. Not once. Github does only one thing, the CI is usually somewhere else so there have less reasons to fail as well... It might be comparing apples and oranges. We use Gitlab at the office and it is constantly slow. Might be our setup I agree, but in t…

To be fair, Over the last 5 years, I've been hit by several Github outages and never been hit with a Gitlab outage. The reason? I don't use Gitlab during my working day. Similarly with this one, I wasn't doing anything on Gitlab when it went down.

Interesting. My issues have been in the evening :). Are you in the US? I am EU based

Re: Gitlab was down

#87

Post by 1337shadow »

oefrha wrote: post #64
1337shadow wrote: post #51

Back in the days GitLab made it clear that it aspires to be a software company rather than an infrastructure company. The reason I favor GitLab over GitHub is that I can install it on a dedicated server and have blazing fast performance, which helps development performance on an every day basis. I've been maintaining a bunch of deployments of all sorts (k8s, docker-compose, baremetal) for the last years for several c…

> have blazing fast performance Sorry, but GitLab has never been blazing fast. The gitlab.com instance is notoriously slow — supposedly improved a lot over the past few years, but still feels pretty sluggish. My self-hosted instance isn’t much better. In fact, a couple of open source maintainer friends looked into migrating to GitLab when GitHub was acquired by MS; they did not precisely because GitLab was too slow.

Let me clarify: git clone/fetch/push on gitlab.com or github.com is sluggish, but on my private instances it's blazing fast, because I get great and un-metered bandwidth from my dedicated servers which might not be the case for everybody / every country.

Another thing: CI starts the very second I push, and since I configure dedicated runners extremely well GitLab makes it easy keep every pipeline stage under 5 minutes, which is critical to me, as such I recon I have acquired countless tricks for that matter.

Also, the ChatOps integration (GitLab to Mattermost or Slack) seems instant for me.

Those factors matter for me because I'm an extremely fast iterator and often iterate on several repositories at the time.

The cherry on the top is that the mirroring between my gitlab instance and github is also blazing fast.

As for the web interface, well they all feel slow to me so I don't spend my time waiting for them so it's ruled out of the equation for me anyway, I'm just far more comfortable with command line anyway.

But, pushing to gitlab prints out the URL to create a pull request from that branch, or to view the existing one, also a time saver that's not available on github, not sure why though.

Re: Gitlab was down

#88

Post by maze-le »

kungtotte wrote: post #73
jlengrand wrote: post #66

I used to be a total Gitlab fanboy. I was going to Sid's meetups back in Utrecht 6 years ago, and he's a model of mine to this time. I would have done anything to stay on the platform, for at home and the office and setup gitlab instances in two different offices. Since somewhere last year, I moved back to Github primarily, and I'm sad to hear that my company is likely to make the same choice soon.The only reason is…

Whenever GitHub is down you see comments saying much the same thing only with the names reversed. The thing that strikes me each time is how fragile everyone's setup is if GitHub/lab is a single point of failure for them... At least gitlab let's you self host, which would let you run backups on offsite hosting meaning zero downtime.

>> At least gitlab let's you self host, which would let you run backups on offsite hosting meaning zero downtime.

Zero downtime but not zero maintainence cost. I think the administration of a full CI/CD environment (not only the gitlab machine, also the runners, the network etc.) are the main factor for this.

Re: Gitlab was down

#89

Post by lima »

jlengrand wrote: post #81
kungtotte wrote: post #73

Earlier quoted context omitted.

Whenever GitHub is down you see comments saying much the same thing only with the names reversed. The thing that strikes me each time is how fragile everyone's setup is if GitHub/lab is a single point of failure for them... At least gitlab let's you self host, which would let you run backups on offsite hosting meaning zero downtime.

Agreed, nobody's perfect. My experience with github is much better though on average. Haven't had a single bad experience personally the past year for my personal stuff. Not once. Github does only one thing, the CI is usually somewhere else so there have less reasons to fail as well... It might be comparing apples and oranges. We use Gitlab at the office and it is constantly slow. Might be our setup I agree, but in t…

>Github does only one thing, the CI is usually somewhere else so there have less reasons to fail as well... It might be comparing apples and oranges.

This is changing with Github Actions.

Re: Gitlab was down

#90

Post by [deleted] »

jlengrand wrote: post #81
kungtotte wrote: post #73

Earlier quoted context omitted.

Whenever GitHub is down you see comments saying much the same thing only with the names reversed. The thing that strikes me each time is how fragile everyone's setup is if GitHub/lab is a single point of failure for them... At least gitlab let's you self host, which would let you run backups on offsite hosting meaning zero downtime.

Agreed, nobody's perfect. My experience with github is much better though on average. Haven't had a single bad experience personally the past year for my personal stuff. Not once. Github does only one thing, the CI is usually somewhere else so there have less reasons to fail as well... It might be comparing apples and oranges. We use Gitlab at the office and it is constantly slow. Might be our setup I agree, but in t…

[deleted]
Post reply on HN