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

101–110 of 140 posts

Re: Gitlab was down

#101

Post by toupeira »

dijit wrote: post #54
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.

What you say is completely fair. I’ve been looking at job postings and watching the way they work too for a little time since it’s all open. DBAs are “ruby devs who have used Postgres” https://about.gitlab.com/jobs/apply/backend-engineer-databas... SREs are “ruby devs who have used docker/kubernetes” (No job listing currently) The only open job labelled “ops” is telling. https://about.gitlab.com/jobs/apply/frontend-e…

GitLab engineer here.

The "Ops" section actually consists of product development teams for features in GitLab itself (the Configure/Monitor "stages"), while the SREs are in the "Infrastructure" department. See https://about.gitlab.com/handbook/engineering/#engineering-d.... But yes, we don't seem to be hiring SREs at the moment, but I assume we'll add more openings in the beginning of next year.

Regarding DBAs, that job you posted is more of a normal Backend Engineer role with a database specialty. We also have dedicated Database Engineer roles:

- https://about.gitlab.com/job-families/engineering/database-e...

- https://about.gitlab.com/job-families/engineering/database-r...

The job description for SREs is here:

- https://about.gitlab.com/job-families/engineering/site-relia...

Re: Gitlab was down

#102

Post by mcny »

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

Earlier quoted context omitted.

> 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 minute…

You should look into git request-pull. I haven't gotten it to work but I'm probably doing it wrong. It should work.

https://git-scm.com/docs/git-request-pull

Re: Gitlab was down

#103

Post by manigandham »

jlengrand wrote: post #97
lima wrote: post #89

Earlier quoted context omitted.

>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.

> This is changing with Github Actions. Well gitlab does artifactory/docker management, security, value stream management, . . . So still

GitHub now has package registries and security scans too, and adding more features to complete the lifecycle.

Re: Gitlab was down

#104

Post by andrelaszlo »

leipert wrote: post #63
andrelaszlo wrote: post #38

Earlier quoted context omitted.

If you just want to try it out, the easiest is often Gitlab Development Kit. gem install gitlab-development-kit gdk init cd gitlab-development-kit gdk run I doubt it will work today though; it's probably pulling everything from Gitlab. For Docker, check out https://hub.docker.com/r/gitlab/gitlab-ce I haven't tried it out for myself but it seems popular :)

The GDK installation has changed a bit (just set it up today, you need to run gdk install and gdk start (instead of run) for example). Please also note that it involves installing dependencies on your local machine, like e.g. Ruby / Postgres, etc. Here is the link to the GDK: https://gitlab.com/gitlab-org/gitlab-development-kit Otherwise I would try the docker container OR just install it with omnibus in a VM: https:…

Oh, thanks. I got that from some old notes since my bookmark didn't work for some reason ;)

For me, running Gitlab locally is extremely heavy (webpack especially). How beefy is your computer, as a Gitlab developer?

Re: Gitlab was down

#105

Post by toupeira »

pearjuice wrote: post #6

I don't want to hijack this thread but what was the end result of the decision of Gitlab not hiring _in_ certain countries anymore? A lot of media coverage when the incident happened but no idea what happened afterwards and can't easily find it.

The discussion is still ongoing, the latest official communication I'm aware of was the blog post at https://about.gitlab.com/blog/2019/11/12/update-on-hiring/

Note that this was always only about excluding certain job roles who have administrative access to production servers, not all jobs in general.

Re: Gitlab was down

#106

Post by chriscool »

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

Earlier quoted context omitted.

> 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 minute…

> pushing to gitlab prints out the URL to create a pull request from that branch

You can use push options to automatically create a pull request and set it up when you push:

https://docs.gitlab.com/ee/user/project/push_options.html

Re: Gitlab was down

#107

Post by toupeira »

tristanperry wrote: post #79
protomikron wrote: post #76

Earlier quoted context omitted.

GitHub's uptime is way better than GitLab. I am not really sure gitlab.com even reaches 99% availability (not to mention 99.9%). GitLab may well be focused on providing full-stack dev-services (VCS, build-server, CI and stuff), but in the end they are a hosting company - and for hosting, uptime is one of the most important metrics. EDIT: 99% was exaggerating, but I got so many 50Xs the last days that it was from time…

I agree that GitHub's uptime is better, but I doubt that Gitlab aren't at 99% availability - that'd mean over 14.4 minutes of downtime each day.

We have some public Pingdom stats at http://stats.gitlab.com/4932705/history, looks like this was the first time we dipped below 99.9% this year (partial outages excluded).

But yeah, our response times have been steadily increasing and could definitely be a lot better ;-)

Re: Gitlab was down

#108

Post by jlengrand »

manigandham wrote: post #103
jlengrand wrote: post #97

Earlier quoted context omitted.

> This is changing with Github Actions. Well gitlab does artifactory/docker management, security, value stream management, . . . So still

GitHub now has package registries and security scans too, and adding more features to complete the lifecycle.

Wasn't aware. Will look into it. Thanks!

Re: Gitlab was down

#109

Post by jeltz »

toupeira wrote: post #101
dijit wrote: post #54

Earlier quoted context omitted.

What you say is completely fair. I’ve been looking at job postings and watching the way they work too for a little time since it’s all open. DBAs are “ruby devs who have used Postgres” https://about.gitlab.com/jobs/apply/backend-engineer-databas... SREs are “ruby devs who have used docker/kubernetes” (No job listing currently) The only open job labelled “ops” is telling. https://about.gitlab.com/jobs/apply/frontend-e…

GitLab engineer here. The "Ops" section actually consists of product development teams for features in GitLab itself (the Configure/Monitor "stages"), while the SREs are in the "Infrastructure" department. See https://about.gitlab.com/handbook/engineering/#engineering-d... . But yes, we don't seem to be hiring SREs at the moment, but I assume we'll add more openings in the beginning of next year. Regarding DBAs, that…

Why is significant Rails experience a requirement for a database engineer position? That will quite drastically limit your options. Yes, it is a useful skill but hardly necessary to do this job. I know a lot of really good database consultants and they can usually identify and fix bad queries in virtually any framework or ORM. The skills are really transferable.

Re: Gitlab was down

#110

Post by tnolet »

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…

Totally off topic: also went to those meetups in Utrecht! They were small fish then. Cray what can happen in ~6 years.
Post reply on HN