GitLab 8.5 released • Hacker News Board

Re: GitLab 8.5 released

#141

Post by sytse » Mon, Feb 22, 2016, 9:06 PM UTC

stormbrew wrote: post #121

dudul wrote: post #115

Earlier quoted context omitted.

For example, a lot of people complain about issues on GitHub. GitLab handles those much better, that could be a compelling reason to move, but somehow it doesn't seem to be enough. Private repo can be useful for early stage of OSS projects. Agreed though that it still feels too much like a clone of GitHub. The UI for example is way to close to the original.

Having used both there's more than enough in either that's bad to justify a switch to the other if you really want to. I personally prefer github's warts to gitlab's. In particular, I find that general site navigation on gitlab is quite tedious and it rarely centres useful information first. But that is very much a qualitative and not a quantitative complaint. The main thing I find extra useful on gitlab is the abili…

Glad you like our WIP function. Do you maybe have any suggestions how we can make navigation better and/or examples of pages where you are missing information?

Re: GitLab 8.5 released

#142

Post by sytse » Mon, Feb 22, 2016, 9:08 PM UTC

dogweather wrote: post #132

josteink wrote: post #107

Looking at this thread here, Gitlab seems to be much more open about their development than Github, and has a real sense of community, yet Github (still) remains the popular option, despite their more community-hostile traditional board-meeting decision process. Is there a gradual shift in the FOSS community towards Gitlab (which in all honesty would make more sense), or am I just seeing the enthusiast in this thread…

GitLab has a ton of strengths, but still has large weaknesses in the area: gitlab.com implementation and design. gitlab.com is the public 'demo' version which people compare to github. It's missing a few key items that would make it appealing to open source developers (and that I'd like to see them prioritize.) E.g.: * Site search. It's been broken for months or possibly years. (Response time > 45 secs., Relevancy is…

I agree we can do a lot better in project discovery on GitLab.com. I do want to mention that https://gitlab.com/explore?utf8=%E2%9C%93&filter_projects=gi... gives results in a few seconds and GitLab itself is the first hit.

Re: GitLab 8.5 released

#143

Post by dhagz » Mon, Feb 22, 2016, 9:14 PM UTC

dogweather wrote: post #132

josteink wrote: post #107

Looking at this thread here, Gitlab seems to be much more open about their development than Github, and has a real sense of community, yet Github (still) remains the popular option, despite their more community-hostile traditional board-meeting decision process. Is there a gradual shift in the FOSS community towards Gitlab (which in all honesty would make more sense), or am I just seeing the enthusiast in this thread…

GitLab has a ton of strengths, but still has large weaknesses in the area: gitlab.com implementation and design. gitlab.com is the public 'demo' version which people compare to github. It's missing a few key items that would make it appealing to open source developers (and that I'd like to see them prioritize.) E.g.: * Site search. It's been broken for months or possibly years. (Response time > 45 secs., Relevancy is…

That will definitely hurt the FOSS community adopting them, but they're becoming very appealing for private projects. At work I use BitBucket, but GitLab now has better looking Issues, and with built-in CI it's becoming hard for me to resist switching.

Re: GitLab 8.5 released

#144

Post by eikenberry » Mon, Feb 22, 2016, 9:19 PM UTC

toyg wrote: post #120

josteink wrote: post #107

Looking at this thread here, Gitlab seems to be much more open about their development than Github, and has a real sense of community, yet Github (still) remains the popular option, despite their more community-hostile traditional board-meeting decision process. Is there a gradual shift in the FOSS community towards Gitlab (which in all honesty would make more sense), or am I just seeing the enthusiast in this thread…

Github's shortcomings only really came to the fore in the last couple of months, due to a combination of factors. GitLab is working hard to exploit the current window of opportunity to make waves. I'm slightly surprised BitBucket is not doing the same, but their Atlassian masters seem more interested in pushing irrelevant features at the moment (like SSO across products I don't care about). It's too early to talk abo…

Atlassian is going after the enterprise market. They don't care about free software developers.

Re: GitLab 8.5 released

#145

Post by balameb » Mon, Feb 22, 2016, 9:28 PM UTC

cheald wrote: post #102

balameb wrote: post #98

Earlier quoted context omitted.

Just to be clear. All we need is the output from the console not the actual backup. What I see from the result your getting is the actual backup command failing. From my experience this might be do to how its executed through the upgrade process and we can have a closer look at what failed when running the create command.

I sent an email, but it looks like if RVM is installed, gitlab-rake may be depending on bundler being installed in the currently-active RVM environment. It looks like RVM may be conflicting with gitlab's bundled Ruby due to RVM setting GEM_PATH and prevents bundler from being found, which causes the upgrade process to fail. Explicitly setting GEM_PATH for the gitlab_rake invocation may fix it. If bundler is available…

Correct the GEM_PATH is conflicting. Thank you for the information provided and your help through our support channel. Here is the public issue for future reference: https://gitlab.com/gitlab-org/gitlab-ce/issues/13689.

Re: GitLab 8.5 released

#146

Post by YorickPeterse » Mon, Feb 22, 2016, 9:29 PM UTC

giancarlostoro wrote: post #137

YorickPeterse wrote: post #118

Earlier quoted context omitted.

Not yet, but I've been thinking of doing so. The difficulty is that you basically have to write the blog post (or at least take a lot of notes) while solving problems as otherwise you'll end up forgetting all the intricate little details.

That's fine, I'm just curious because you usually learn a great deal. If anything the biggest performance changes could be nice, though it may mostly be small tid bits here and there (though large overall). Thanks for all you guys did!

I still have a bunch of notes laying around from the changes we made for 8.5 so I'll take a look at those. For future changes (except maybe small ones) I'll see if I can just write down 1 or 2 sentences what I did _after_ I did it, stringing together a blog post from that should be easier than doing it from scratch.

I created an issue about this so I won't forget: https://gitlab.com/gitlab-com/www-gitlab-com/issues/568

Re: GitLab 8.5 released

#147

Post by mrmondo » Mon, Feb 22, 2016, 9:41 PM UTC

Another great release in an incredibly fast turn around time, well done to the team and everyone that's contributed.

Re: GitLab 8.5 released

#148

Post by sytse » Mon, Feb 22, 2016, 9:43 PM UTC

YorickPeterse wrote: post #146

giancarlostoro wrote: post #137

Earlier quoted context omitted.

That's fine, I'm just curious because you usually learn a great deal. If anything the biggest performance changes could be nice, though it may mostly be small tid bits here and there (though large overall). Thanks for all you guys did!

I still have a bunch of notes laying around from the changes we made for 8.5 so I'll take a look at those. For future changes (except maybe small ones) I'll see if I can just write down 1 or 2 sentences what I did _after_ I did it, stringing together a blog post from that should be easier than doing it from scratch. I created an issue about this so I won't forget: https://gitlab.com/gitlab-com/www-gitlab-com/issues/5…

Awesome!

Re: GitLab 8.5 released

#149

Post by mrmondo » Mon, Feb 22, 2016, 9:44 PM UTC

Keats wrote: post #57

praseodym wrote: post #54

Their performance graph shows response timings up to 25 seconds [1]. GitHub's mean web response time goes up to 200 milliseconds. The difference is two orders of magnitude. Is GitLab really that much slower?! [1] https://about.gitlab.com/images/8_5/issue_timings.png [2] https://status.github.com/

It is extremely slow. We tried it on a 1go droplet and it felt slow with 2 users but can't beat that £0 price.

Have you tried running GitHub EE on something of the same spec? It's terrible to near impossible and it doesn't include nearly as many of the features as Gitlab. We have been running Gitlab for 100~ employees for well over a year on a single, medium/low specced VM and its lightning quick, so much so that when Devs/Ops have to use GitHub you can hear the sighs around the office!

Re: GitLab 8.5 released

#150

Post by Afforess » Mon, Feb 22, 2016, 9:46 PM UTC

eikenberry wrote: post #144

toyg wrote: post #120

Earlier quoted context omitted.

Github's shortcomings only really came to the fore in the last couple of months, due to a combination of factors. GitLab is working hard to exploit the current window of opportunity to make waves. I'm slightly surprised BitBucket is not doing the same, but their Atlassian masters seem more interested in pushing irrelevant features at the moment (like SSO across products I don't care about). It's too early to talk abo…

Atlassian is going after the enterprise market. They don't care about free software developers.

That's a poor strategy. All developers start out as free software developers, then gain employment. I persuaded my work to purchase Gitlab EE licenses, due to ease of use and it's excellent features & support. I can't imagine I'd say the same of Atlassian products.

Capture awareness / interest early.