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

131–140 of 140 posts

Re: Gitlab was down

#131

Post by toupeira »

dijit wrote: post #115
toupeira wrote: post #101

Earlier quoted context omitted.

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…

Hi Toupeira, I didn't find some of those jobs, so thanks for linking them. As a side note I just went through those job descriptions and I -really- like the layout. On topic: Unfortunately they really do prove my point. There is a very strong focus on "strong" programming skills which is rather undefined. It's literally mentioned in every single role description. The overwhelming majority of staff that knows how to r…

That's certainly a valid concern! From my perspective, the programming skills in these job descriptions are one requirement among many others, and I'm not sure how much weight it really has in the hiring process for these roles, especially if your other skills are a good enough match.

We do have this note on all job pages, which maybe should be more prominent:

> Avoid the confidence gap; you do not have to match all the listed requirements exactly to apply.

Some amount of general programming experience is definitely required though, since SREs and DBEs frequently have to dig into our codebase and things like Ansible runbooks. And especially regarding SQL, a lot of it is heavily abstracted not only through the Rails ORM but also our own code.

Found some other jobs that focus less on programming, though we don't have current openings for most of these either:

- https://about.gitlab.com/job-families/engineering/cloud-nati...

- https://about.gitlab.com/job-families/engineering/infrastruc...

- https://about.gitlab.com/job-families/engineering/monitoring...

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

- https://about.gitlab.com/job-families/engineering/vulnerabil...

We don't seem to have a good overview of all roles, I found these through https://gitlab.com/gitlab-com/www-gitlab-com/tree/master/sou... :)

Re: Gitlab was down

#132

Post by ktsmith »

kburman wrote: post #4

> Website, API, Git (ssh and https), Pages, Registry, CI/CD, Background Processing, Support Services, packages.gitlab.com, customers.gitlab.com, version.gitlab.com, forum.gitlab.com How come all of them are down all at once.

You can look through what happened here: https://gitlab.com/gitlab-com/gl-infra/production/issues/142...

Re: Gitlab was down

#134

Post by FanaHOVA »

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

Earlier quoted context omitted.

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, or to view the existing one, also a time saver that's not available on github IIRC I’ve seen that recently with GitHub too. Not very useful to me though since I use magit for almost all git-related operations.

Yea GitHub has had this option for at least a couple months now.

Re: Gitlab was down

#135

Post by leipert »

andrelaszlo wrote: post #104
leipert wrote: post #63

Earlier quoted context omitted.

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?

I have got a 16 GB MacBook from 2018.

Funny that you mention Webpack, I am part of the webpack working group and we are trying to improve developer experience:

https://about.gitlab.com/company/team/structure/working-grou...

We were able to reduce memory consumption quite a bit, but we are working on different other improvements.

Re: Gitlab was down

#136

Post by 1337shadow »

erikbye wrote: post #119
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.

Not to mention consuming way too much memory. I prefer Gitea, or cgit if I need even less features.

Indeed, you can use drone-CI with Gitea that's also an option. But for now I find Gitlab-CI still slightly better: graphical representation of the pipeline, editable environment variables, review-stop jobs to clean up review deploys, automatic review-stop on MR merge ... Anyway, I run both because some people really want to keep their main repo activity on GitHub "for visibility" (for me that doesn't stand: I use gitlab->github mirroring feature as such my work is still published on github)

Re: Gitlab was down

#137

Post by 1337shadow »

stevekemp wrote: post #80
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…

> the upgrade process has always been pretty smooth By contrast I've managed a self-hosted install a while back, upgrades regularly broke as much as they fixed. For example the time when LDAP logins all failed, the gitlab-pages stopped working, and more. That's on top of the constant UI churn with the side-menu, and similar changing from release to release with no rhyme or reason. I wanted to like it, and did like th…

For me they got the UX/UI pretty right since last release, I enjoy it both on mobile and desktop devices.

Anyway, for CI-runner setup, I have a one-liner that worked for me: bigsudo install lean_delivery.gitlab_runner @somehost gitlab_ci_token=yourcommand gitlab_host=yourlabs.io gitlab_runner_limit=4 gitlab_version=11.6

But also a docker run does the job... Well, there's still registration of runner that I did manually, but I just checked ansible documentation and it really looks like I got a fair chance to achieve that too, given all the new modules ansible got since 2.8 to deal with gitlab, including gitlab_runner and gitlab_runners modules: https://docs.ansible.com/ansible/latest/modules/gitlab_runne...

So yes, Gitlab strives to keep development and releases coming, that means sometimes foundations move, and that there's a learning curve too, I understand that some people may not like that, but as a dev myself I like it this way, and at the end of the day my team iterates great with GitLab-CI, we got automated review-deploys in less than 5 minutes with just docker-compose and that's really helpful to keep the master branch clean, this allows features to be merged only after they have received product team approval so that's a big win. With GitHub you can also do it with Drone-CI which you might like better because it's easier to setup even though it remains behind GitLab-CI in terms of features that matter to me.

Re: Gitlab was down

#138

Post by mikekchar »

jlengrand wrote: post #86
mikekchar wrote: post #84

Earlier quoted context omitted.

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

I'm in Japan :-)

Re: Gitlab was down

#139

Post by andrelaszlo »

leipert wrote: post #135
andrelaszlo wrote: post #104

Earlier quoted context omitted.

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?

I have got a 16 GB MacBook from 2018. Funny that you mention Webpack, I am part of the webpack working group and we are trying to improve developer experience: https://about.gitlab.com/company/team/structure/working-grou... We were able to reduce memory consumption quite a bit, but we are working on different other improvements.

Great! I see you were actually involved in one of the problems that bit me (8 GB...). https://gitlab.com/gitlab-org/gitlab-development-kit/issues/...

Small world :)

Post reply on HN