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

Gitlab 9.0

about.gitlab.com

Post reply on HN
Print view View original

111–120 of 164 posts

Re: Gitlab 9.0

#111

Post by jbk »

victorwu wrote: post #104
jbk wrote: post #93

We've been using gitlab for most VideoLAN projects, and are moving towards it for all of them (including vlc and x264). A lot of things are great, and going in the right direction, but the issues tracker is really lacking. The lack of custom fields, that you find in all other bugtrackers except github, and the lack of dependent issues are really blocking us to move full to gitlab. And the biggest issue is that they'r…

You are referring to this one right? https://gitlab.com/gitlab-org/gitlab-ee/issues/1906 . Yes, it is currently marked as an EE feature. And Sid linked to the dependent issues feature below. Both of these features are not scheduled for development yet. We scope work out month to month, so we can't promise anything regarding those at this time. But we are discussing them as you see in the issues and considering how th…

How can we help? Can we help coding?

Re: Gitlab 9.0

#112

Post by nikcub »

nik736 wrote: post #36

As much as I love GitLab the UI/UX is still very weak compared to GitHub. And the sidebar change is something in the completely wrong direction. You should also really check out how it looks on a 4k screen.

They've set a very high bar for GitLab because not only is GitHub a great repository and project UI, it is one of the best overall application interfaces out there.

It's difficult being compared with GitHub and bucketed with them from a UI perspective, but GitLab really are holding their own and seem up to it

Re: Gitlab 9.0

#113

Post by tmaczukin »

garou wrote: post #79

I am having problem with de CI/CD after update: ``` Running with gitlab-ci-multi-runner 9.0.0[...] Cloning repository... Cloning into '/builds/xxxxxxx'... warning: You appear to have cloned an empty repository. Checking out xxxxxxx as master... fatal: reference is not a tree: xxxxxx ```

For other who are seeing this issue: 'gitlab-ctl reconfigure && gitlab-ctl restart' should resolve this problem without a need to reboot the machine.

The problem is tracked in https://gitlab.com/gitlab-org/gitlab-ce/issues/29855

Re: Gitlab 9.0

#114

Post by mydigitalself »

jbk wrote: post #93

We've been using gitlab for most VideoLAN projects, and are moving towards it for all of them (including vlc and x264). A lot of things are great, and going in the right direction, but the issues tracker is really lacking. The lack of custom fields, that you find in all other bugtrackers except github, and the lack of dependent issues are really blocking us to move full to gitlab. And the biggest issue is that they'r…

> non-open-source version, which we cannot use...

is it a function of cost, or otherwise?

Re: Gitlab 9.0

#115

Post by buxtehude »

victorwu wrote: post #88
itwy wrote: post #71

The sidebar took a step backward in my opinion. I am missing the 'pin' option.

Thanks. Feel free to add feedback to the ongoing discussion here: https://gitlab.com/gitlab-org/gitlab-ce/issues/29835 .

Why did you remove the sidebar + pin again??

When you removed the sidebar last time - users of GitLab lobbied you hard to get that pin in there so they could keep that sidebar open at all times.

These kind of changes make me feel like you're not understanding (respecting) your customers' needs (desires).

Re: Gitlab 9.0

#116

Post by buxtehude »

buxtehude wrote: post #115
victorwu wrote: post #88

Earlier quoted context omitted.

Thanks. Feel free to add feedback to the ongoing discussion here: https://gitlab.com/gitlab-org/gitlab-ce/issues/29835 .

Why did you remove the sidebar + pin again?? When you removed the sidebar last time - users of GitLab lobbied you hard to get that pin in there so they could keep that sidebar open at all times. These kind of changes make me feel like you're not understanding (respecting) your customers' needs (desires).

Sorry just to be clear - I really like GitLab - and I feel GitLab tries hard to make a great product for their users - and clearly they have a good understanding of the development community. It's just that I felt this issue had already been discussed and resolved - to be yet again undone. So just feeling frustrated we have to go through this again.

Re: Gitlab 9.0

#117

Post by Snappy »

ianwalter wrote: post #73
connorshea wrote: post #33

Earlier quoted context omitted.

Thanks for switching to GitLab, glad to hear you're loving it! :D We have this demo from our most recent summit where we put together an entire GitLab instance in ~20 minutes on a Kubernetes cluster, though I'm not sure that's exactly what you want? https://about.gitlab.com/2017/01/23/video-tutorial-idea-to-p... We also have some documentation on integrating with Kubernetes here: https://docs.gitlab.com/ee/user/proje…

The integration with Kubernetes looks pretty cool so far. Is there any consideration being given to integrating with Docker Swarm Mode?

We're hoping to work with the community to support all container schedulers [1].

But right now we're focused on deepening the integration on Kubernetes so it's a great end-to-end experience.

[1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/20199

Re: Gitlab 9.0

#118

Post by buxtehude »

victorwu wrote: post #9
ploggingdev wrote: post #3

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.

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 should realize that enough developers find great utility in that sidebar.

Re: Gitlab 9.0

#119

Post by mydigitalself »

apocalyptic0n3 wrote: post #74
mydigitalself wrote: post #68

Earlier quoted context omitted.

I'm afraid it gets a little worse. In an attempt to simplify some of the settings pages, deploy keys were moved onto the repository settings page. https://gitlab.com/gitlab-org/gitlab-ce/issues/29667 We need to do something about this very soon, so please keep an eye on that issue. We're going to be doing some more work on settings pages, hopefully in 9.2 and make them a lot better. https://gitlab.com/gitlab-org/gitl…

So they are on the main Project Settings page as of 9.0? If that's the case, we will avoid upgrading until that is changed because that page will become fairly unusable in our case, both in terms of speed and general UX because our Deploy Keys page is currently 20,777px tall. That is a lot of scrolling to have to deal with. I will subscribe to those issues and hopefully it will improve. As of now, though, that is a c…

No not the main project settings page. Settings -> Repository and it's right at the bottom, so no more scrolling than you are used to.

Re: Gitlab 9.0

#120

Post by dimitrieh »

chetanahuja wrote: post #87
danial wrote: post #35

Congratulations on shipping 9.0. It's great to see a lot of improvements. Being able to reorder issues in the board is a welcome change. The subgroups is an interesting feature. I look forward to playing with it more. I am still waiting on the ability to view issues on a board across a group (or now, a subgroup). Since Gitlab projects are repo-centric, I have hard time tracking issues across many repositories in a si…

"Since Gitlab projects are repo-centric" This seems to be the huge blind spot on gitlab product design. Everything is tied to git repo's while in the real world installs, users want global views of things which go across git-repos. I suspect this comes from starting off as a github clone, which has it's own constraints as a product (and it's public face).

Hi, we are moving more and more into the direction of going multi repo/multi project. Subgroups is the most significant step forwards for this. Expect to see cross project pipelines, management feature, monitoring etc
Post reply on HN