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

GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

about.gitlab.com

Post reply on HN
Print view View original

11–20 of 58 posts

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#11

Post by pknopf »

marmaduke wrote: post #6

I like GitLab but noticed my Docker container running it is steadily requiring more memory to run smoothly. It’s sitting at 12GB right now, which is a little too high for my taste. I wish there were ways to reduce this.

I occasionally have to rm my docker instance and recreate it.

I'm not sure what it's doing, but at least it's an easy fix.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#12

Post by wickchuck »

sebazzz wrote: post #7

How well does on-premises Gitlab work? Can it run relatively maintenance-free? I heard some negative stories, but I don't know what is true. My team of devs doesn't have a dedicated sysadmin.

I've been managing a small instance since version 5. There have been a few hiccups here and there, but mostly due on my part to not reading the release/upgrade notes carefully enough. Since version 8/9 it has been absolutely pain free. Run apt-get update then apt-get upgrade wait a bit and enjoy the new release!

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#13

Post by baaym »

I've been enjoying GitLab at my last three employers now, with the CI integration being the most liberating feature compared to the traditional CI providers. Especially the Docker CI runner gives you a great integration test environment, and I'm impatiently waiting for this MR [0] that will allow dependant containers to also talk to each other. It's the last missing piece for my ideal CI setup.

[0] https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1...

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#14

Post by meddlepal »

Used GitLab maybe 5 years ago now? I was impressed with it despite its immaturity. These new features look great though.

I found the operation of on-prem GitLab to be a bit of a PITA back then, has that changed? There was a whole bunch of rake tasks and junk you needed to run to upgrade and it required a shutdown of the system.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#15

Post by cevn »

meddlepal wrote: post #14

Used GitLab maybe 5 years ago now? I was impressed with it despite its immaturity. These new features look great though. I found the operation of on-prem GitLab to be a bit of a PITA back then, has that changed? There was a whole bunch of rake tasks and junk you needed to run to upgrade and it required a shutdown of the system.

Upgrade is usually as simple as an apt update && apt upgrade for me. Every once in a while they change tables in a non backwards compatible way and you have to force allow it or something. It's all very easy though.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#16

Post by lbotos »

meddlepal wrote: post #14

Used GitLab maybe 5 years ago now? I was impressed with it despite its immaturity. These new features look great though. I found the operation of on-prem GitLab to be a bit of a PITA back then, has that changed? There was a whole bunch of rake tasks and junk you needed to run to upgrade and it required a shutdown of the system.

It's a lot easier, and dead simple to run a small single server install. When you start scaling, it gets a little harder, but our vision it to leverage K8s for that type of deployment.

(Source: work at GitLab, and I wouldn't If we had to manage the infra by hand vs. omnibus/k8s)

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#17

Post by lbotos »

marmaduke wrote: post #6

I like GitLab but noticed my Docker container running it is steadily requiring more memory to run smoothly. It’s sitting at 12GB right now, which is a little too high for my taste. I wish there were ways to reduce this.

One of our Engineering Fellows is working Memory Optimization across the entire product this quarter. We are aware, and starting on it!

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#18

Post by jmarneweck »

meddlepal wrote: post #14

Used GitLab maybe 5 years ago now? I was impressed with it despite its immaturity. These new features look great though. I found the operation of on-prem GitLab to be a bit of a PITA back then, has that changed? There was a whole bunch of rake tasks and junk you needed to run to upgrade and it required a shutdown of the system.

When I first used Gitlab on SmartOS it was a pain to upgrade manually.

I more recently used Gitlab on Ubuntu using their omnibus package for Ubuntu and the upgraded over multiple versions to get onto a later version of Gitlab. The upgrade process was a lot smoother (no fighting to build gems on SmartOS and patching all over the show to get gems and other dependencies to compile).

I also did a MySQL to Postgresql migration. You have a bit of downtime with the process which chef sorts things out post upgrade of the omnibus package. I did turn the unicorns and disabled ssh logins while I was upgrading the omnibus package just incase something went wrong during the upgrade.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#19

Post by notus »

I've heard some people saying that the recent free private repos from github could potentially hurt or impact gitlab. I'm not entirely sure why since it is free stuff and not things you are paying for. Is there any merit to that or was I just listening to the wrong person? I'm thinking about applying there

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#20

Post by tyldum »

meddlepal wrote: post #14

Used GitLab maybe 5 years ago now? I was impressed with it despite its immaturity. These new features look great though. I found the operation of on-prem GitLab to be a bit of a PITA back then, has that changed? There was a whole bunch of rake tasks and junk you needed to run to upgrade and it required a shutdown of the system.

Mainly just apt-get these days. Occasionally something is deprecated in the config file, but the release notes are very clear. Never had an issue and our omnibus install has been chugging along since they introduced enterprise version back in the days.
Post reply on HN