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

91–100 of 164 posts

Re: Gitlab 9.0

#91

Post by jobvandervoort »

chetanahuja wrote: post #84

The new enhancements seem very promising. We've been using gitlab for our internal use for a while now. Having said that, every time a new gitlab release comes around, I always looks for updates in one area expectantly but mostly left unsatisfied. And that is, separation of the concept of Project from "one git repo" E.g., I want to manage a project that ties in issues from various different git repositories. It's pre…

One of the high level goals I set for this year is scaling up to projects that consist of more than a single repository.

That means CI that spans multiple projects [0], higher abstraction of issue management [1], formal relationships between issues [2] and more.

Having a global wiki or higher level wiki should also be part of that [3], I think.

[0]: https://gitlab.com/gitlab-org/gitlab-ee/issues/933

[1]: https://gitlab.com/gitlab-org/gitlab-ee/issues/928

[2]: https://gitlab.com/gitlab-org/gitlab-ce/issues/4058

[3]: https://gitlab.com/gitlab-org/gitlab-ce/issues/4037

Re: Gitlab 9.0

#92

Post by prh8 »

victorwu wrote: post #45
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…

Like Job mentioned, we've been ramping up issue boards and groups (subgroups now) rapidly in the past few releases. Group-level issue boards are definitely on our radar. Feel free to leave any comments on the issue itself that Job linked: https://gitlab.com/gitlab-org/gitlab-ee/issues/928 . Currently we are considering bringing all the issues of all projects (that are in the same group) into one location, i.e the gro…

When you say team-based, do you mean as in organizations? That would be a huge killer feature. I've only been part of an org on GH, but org wide issues/boards/communication is a huge missing piece.

Re: Gitlab 9.0

#93

Post by jbk »

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're discussing to do it, but only in the non-open-source version, which we cannot use...

Re: Gitlab 9.0

#95

Post by nik736 »

victorwu wrote: post #52
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.

Thank you for the feedback. The sidebar is indeed oft-discussed. And we don't claim we have all the right answers. We work hard every iteration to make the best decision, ship updates, and get feedback. This is the issue where we discussed the sidebar change. Feel free to see what contributed to the decision. https://gitlab.com/gitlab-org/gitlab-ce/issues/26200 This is the ongoing issue to discuss the change and any…

Is it possible to have the navbar fixed as well and not only the content?

Re: Gitlab 9.0

#96

Post by bronson »

frikk wrote: post #19
tomc1985 wrote: post #8

Gitlab was really promising for my colleagues and I, but its inability to host git repos on the url root (aka gitrepo.mycompany.com/product.git) without hacking means its a no-go as we're not particularly inclined to redo all our development, deployment, and testing infrastructure. We use git a lot in our organization, including customer-facing stuff, so it would be a large transition. Also stubborn coworkers who don…

What if you just set up an nginx reverse proxy? gitrepo.mycompany.com/product.git --> reverse proxy to git.mycompany.com/gitrepo/product.git Should be straight forward in nginx

Presumably this falls afoul of the "without hacking" requirement.

Re: Gitlab 9.0

#97

Post by sytse »

jamesmiller5 wrote: post #90
sytse wrote: 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…

Taking a look at Gitaly & the conversations around it, I don't see much in the way of consensus. Are you using Redis for the distributed lock or is this still a centralized system? My query being you can effectively use the native pre-receive hooks & wrap the git shell to allow consensus without needing to replace git with an RPC system like Gitaly.

Gitaly is still a centralized system. It shards the git repositories over multiple git servers in one datacenter.

We looked into Git Ketch https://www.infoq.com/news/2016/02/google-kick-starts-git-ke... for a distributed system based on hooks. But this requires a sync per repository (very slow with 100k+ repos per server) and it is no longer actively being worked on by Google.

Re: Gitlab 9.0

#98

Post by sytse »

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…

Thanks for using GitLab. We have open sourced features based on your request before https://news.ycombinator.com/item?id=10931690

I can't promise anything regarding these features. Especially custom fields are a typical EE feature in our perspective. The dependent issues feature proposal https://gitlab.com/gitlab-org/gitlab-ce/issues/4058#note_249... is still on the CE tracker but I'm not sure what it's future is.

Re: Gitlab 9.0

#99

Post by ianleeclark »

tomc1985 wrote: post #58
ianleeclark wrote: post #54

Earlier quoted context omitted.

If I remember right, nginx doesn't support ssh + http(s) on the same port. I'd be happy to learn this isn't correct, though because my personal server only is allowing http through.

Generally speaking, you cannot bind more than one service to a port on a given interface

Yeah, that's the issue i had ran into. I was `listen`ing on 80, but wanted to multiplex ssh+http on the same port and nginx didn't support it.

Re: Gitlab 9.0

#100

Post by GordonS »

sytse wrote: post #49
GordonS wrote: post #44

Earlier quoted context omitted.

Well, IMO the Github UI has been taking some steps backwards recently. If Gitlab keeps improving and Github worsening, they'll be at parity before too long

We certainly don't want to win in a race to the bottom. To get an idea what our UX team is working on please see their update from this Monday: Video https://www.youtube.com/watch?v=TMdw-plNfDQ Slides https://docs.google.com/presentation/d/1LM6wHxGVRwHwQvGJiXwF...

I imagined you'd meet in the middle, rather than at the bottom!

I like what you guys are doing - my comment was more meant as a well-natured jibe against the recent Github changes, which I'm really struggling to like (the black header a few weeks ago, and today the search results interface).

Post reply on HN