Live data from Hacker News

Gitlab 9.0

about.gitlab.com

141–150 of 164 posts

Re: Gitlab 9.0

#141

Earlier quoted context omitted.

What's sad is that this isn't the first time GitLab UX/UI peeps have tried to remove the sidebar. 9 months ago we went through a very similar version of this: https://gitlab.com/gitlab-org/gitlab-ce/issues/18542 Can we just all agree to keep the damn sidebar available - if UX wants to remove it, fine, as long as users have the ability to easily permanently pin it back open if they wish to do so. By now GitLab UX shou…

Perhaps the 'sad'/'damn sidebar'/'should realize' passive-aggressive entitlement doesn't help?

Yes, I'm sure Gitlab's engineers make technical decisions based on this guy's tone in Hacker News comments.

Re: Gitlab 9.0

#142
Awesome release!

What do people use to keep up to date with all the non-stop Gitlab releases? I used to use sandstorm but their port is very outdated by now (same goes for bitnami). I switched to cloudron and it has served me well but I am always on the look out for other solutions. On a side note, if you use the omnibus packages, are you a full time (or even part-time) sysadmin?

Re: Gitlab 9.0

#143
post #6

Earlier quoted context omitted.

Great to hear you notice the performance improvements. We're very happy with the improvements but we still have long way to go. We want the 99% latency under 1s and right now it is 2s: https://drive.google.com/file/d/0BzQDcBnEfNRZSTZYVXlyc1FGdEk... There are some controller timings that are red https://drive.google.com/a/gitlab.com/file/d/0BzQDcBnEfNRZZV... And the git access timings are a sea of red https://drive.go…

Looks like those last two screenshots are Grafana - do you mind sharing the dashboard JSON for those views? Very cool!

Thanks. Most of our monitoring is public on http://monitor.gitlab.net/ the things I showed are not because we're still working to make Prometheus work with multi process applications. I'm not sure the Json is public.

Re: Gitlab 9.0

#144

Awesome release! What do people use to keep up to date with all the non-stop Gitlab releases? I used to use sandstorm but their port is very outdated by now (same goes for bitnami). I switched to cloudron and it has served me well but I am always on the look out for other solutions. On a side note, if you use the omnibus packages, are you a full time (or even part-time) sysadmin?

Using omnibus (with backups), it's as simple as an 'aptitude upgrade' for us

Re: Gitlab 9.0

#145

Earlier quoted context omitted.

Perhaps the 'sad'/'damn sidebar'/'should realize' passive-aggressive entitlement doesn't help?

Yes, I'm sure Gitlab's engineers make technical decisions based on this guy's tone in Hacker News comments.

Maybe they just feel bad when they are going to sleep.

Re: Gitlab 9.0

#146
post #9

Earlier quoted context omitted.

The ongoing discussion regarding the sidebar/navigation is here: https://gitlab.com/gitlab-org/gitlab-ce/issues/29835 . Thanks again for the feedback.

What's sad is that this isn't the first time GitLab UX/UI peeps have tried to remove the sidebar. 9 months ago we went through a very similar version of this: https://gitlab.com/gitlab-org/gitlab-ce/issues/18542 Can we just all agree to keep the damn sidebar available - if UX wants to remove it, fine, as long as users have the ability to easily permanently pin it back open if they wish to do so. By now GitLab UX shou…

I sincerely apologize if the tone in my post offends anyone - I let my frustration with this issue get the better of me while writing my comment.

However, I do stand behind the main points of what I wrote:

1. It's disappointing and frustrating to see what is almost the same issue coming up only 9 months later (please look at the link I shared above), where now I'm seeing all the same arguments in favor and against the side bar in these comments as well as in the new related issue thread. We are going through almost the same exercise again.

2. On removing the sidebar - allowing the sidebar to appear and be pinned would be a more inclusive UI/UX choice. Please allow us to pin it again.

I will also add that over the last 1.5 years we've been using GitLab EE the GitLab team has been awesome. I'm continually amazed at how quickly many feature requests become part of GitLab.

Re: Gitlab 9.0

#147
post #80

Earlier quoted context omitted.

Most of CD including deployments already works for private projects, it is only the auto deploy https://docs.gitlab.com/ee/ci/autodeploy/index.html that doesn't work yet. We would all like to see auto deploy working with private projects and it is scheduled for 9.1 If you don't want to use GitLab.com to host your code you can install GitLab yourself or use the mirroring function in GitLab to deploy code hosted elsewh…

will just wait for "Gitlab.com" to get the functionality - is there any lag between Gitlab version upgrade and "Gitlab.com" using the upgraded Gitlab version ? Will wait it out for Gitlab 9.1 :) Thank you for the amazing work.

GitLab.com has RCs weeks before the official release.

And you're welcome.

Re: Gitlab 9.0

#148
post #9

The performance improvements are very noticeable : general page load times, pushing code to gitlab is as fast as github now and the commit messages load insanely fast, compared to a few months ago where loading commit messages in the UI used to take at least a couple of seconds. I don't follow gitlab development too closely, but they seem to have focused a lot on improving cache performance. But one change that I did…

The ongoing discussion regarding the sidebar/navigation is here: https://gitlab.com/gitlab-org/gitlab-ce/issues/29835 . Thanks again for the feedback.

Yeah I miss the sidebar too, it annoyed me and our devs when the pinning was broken and then when there were less items in it.

It felt like without the side bar there is wasted screen realestate that could have project related options or navigation in the side bar.

As resolutions and screens get larger I'm a strong believer that as long as you don't over complicate or make the interface too busy, you shouldn't waste ⅔ of a web site with white space.

Regardless, very happy with 9.0 otherwise, another fantastic release from the team and contributors.

Re: Gitlab 9.0

#149

Awesome release! What do people use to keep up to date with all the non-stop Gitlab releases? I used to use sandstorm but their port is very outdated by now (same goes for bitnami). I switched to cloudron and it has served me well but I am always on the look out for other solutions. On a side note, if you use the omnibus packages, are you a full time (or even part-time) sysadmin?

Using omnibus (with backups), it's as simple as an 'aptitude upgrade' for us

Have you just setup a cronjob for backups? And do you also test somehow that those backups work (or rely on gitlab doing the right thing?) Or maybe you use server snapshots? Also how how did you go about SSL?

Re: Gitlab 9.0

#150
post #136

Earlier quoted context omitted.

Currently running gitlab over docker on a dedicated 8 core system with 32G of ram, it routinely uses 9G of that for barely 30 users. (it's the only thing running on that physical host) So, keep that in mind.

Which version of gitlab? Didn't they reduce memory demands in a recent release?

I keep it updated; it's now version 9 and still consuming 7G

                total       used       free     shared    buffers     cached
   Mem:         31974      13984      17989         12        871       6047
   -/+ buffers/cache:       7066      24907
   Swap:        16367
The UI counts 10G for some reason.

http://i.imgur.com/edAceQx.png

Post reply on HN