Live data from Hacker News

Gitlab 13.1

about.gitlab.com

11–20 of 90 posts

Re: Gitlab 13.1

#11
It's great and impressive how quick Gitlab moves in adding new features.

But if I have a Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them.

And that on every single repo it places these Add License/Contributors etc buttons front and centre even though for 99% of internal projects they serve no purpose.

Every release Gitlab seriously needs to step back and think about how to simplify the interface. Because it's starting to get a bit ridiculous.

Re: Gitlab 13.1

#12

If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly. Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed. I let the page run for 30 seconds and: * CPU usage on two cores was at 100% * 2,94…

GitLab technical evangelist here. I can't seem to reproduce this - maybe it's uBlock Origin? Are you sure it's the default configuration? What were the requests to - just to the main HTML page?

Yes, the page infinitely navigates back to itself resulting in a whole page refresh.

Re: Gitlab 13.1

#14

The alert integration looks interesting, but the screenshots for code intelligence look awful. Who decided to use a super light shade of gray on a white background?

Their UI has a lot of these annoying issues and they never seemed to get around to fixing them.

My other favourites:

1) UI is all muted and grey which is great because it allows you to focus on your code, issues etc. Well except for the Thumbs Up/Down buttons which are a bright yellow and the only thing to stand out. And it's a feature that serves no purpose in most cases.

2) Report Abuse button is next to the New Issue button. But it's given the same size and prominence. Is abuse really as common as creating new issues ?

3) Backgrounds. Some are light grey. Some are dark grey. Some buttons background is filled, others solid.

Re: Gitlab 13.1

#15

If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly. Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed. I let the page run for 30 seconds and: * CPU usage on two cores was at 100% * 2,94…

GitLab technical evangelist here. I can't seem to reproduce this - maybe it's uBlock Origin? Are you sure it's the default configuration? What were the requests to - just to the main HTML page?

Same issue here as the original post and similar extensions. I followed the suggestion of clearing cookies for about.gitlab.com and it doesn't help.

Re: Gitlab 13.1

#16

"This month's Most Valuable Person (MVP) is Jacopo Beschi " What a cool company culture. telling people they are doing good in person is nice, telling it to them and also sharing it with the world is great

GitLab employee here:

The MVPs are not employees, but community contributors as outlined here: https://about.gitlab.com/community/mvp/

But yes, I agree: it is very nice to share the achievements of our OSS contributors with the world :)

Re: Gitlab 13.1

#17

It's great and impressive how quick Gitlab moves in adding new features. But if I have a Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them. And that on every single repo it places these Add License/Contributors etc buttons front and centre even though for 99% of internal projects they serve no purpose. Every release Gitlab seriou…

This comment makes a lot of good points.

I think we can stop recommending License and Contributors since GitLab is mostly used for closed source software. The templates will still be there but just not suggested until you started to create a new file.

And you should be able to disable everything but the repo if you want to. And of course you can disable the repo as well if you just want the planning features for example.

Re: Gitlab 13.1

#18

It's great and impressive how quick Gitlab moves in adding new features. But if I have a Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them. And that on every single repo it places these Add License/Contributors etc buttons front and centre even though for 99% of internal projects they serve no purpose. Every release Gitlab seriou…

Yes agree completely. I'd love to whittle down the noise.

Re: Gitlab 13.1

#19

With every release I wonder why our team is even paying for Gitlab Bronze. It seems to offer no value at all, might as well go for the free tier and save a thousand dollars a year.

Merge Request Reviews was moved to core as part of this release.

Yes, this update basically reduced the value of Bronze significantly as there were no relevant new features coming to Bronze and those that we were paying for are now in the free tier.

Re: Gitlab 13.1

#20

It's great and impressive how quick Gitlab moves in adding new features. But if I have a Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them. And that on every single repo it places these Add License/Contributors etc buttons front and centre even though for 99% of internal projects they serve no purpose. Every release Gitlab seriou…

> It's great and impressive how quick Gitlab moves in adding new features.

Don't trust their feature list, they often "forget" to use it themselves. Many of those features are there to tick the box and daze executives, but are barely usable in practice.

It took them a year to start supporting Kubernetes clusters with RBAC, they didn't use autodevops for their own releases, even for simple components, nor any kubernetes integration, monitoring, feature flags, Geo, backup procedure. Who in the right mind is going to enable Web Application Firewall feature, when rules exceptions cannot be configured?

Somewhere in comments here will be reply from Gitlab employee, saying that dogfooding is something they are constantly working on, it doesn't matter. What they should be doing is to update documentation pages with feature maturity level and have a block of links to most popular bugs related to the feature, so that poor devops engineers don't have to rediscover all the pain and come prepared.

Just to be clear, Gitlab is an awesome tool, it is just not as awesome as their marketing wants us to believe.

Post reply on HN