Live data from Hacker News

GitLab 8.5 released

about.gitlab.com

71–80 of 246 posts

Re: GitLab 8.5 released

#71
post #5

I've moved all my private repos to Gitlab based on the chat on here and other places recently RE Github, Gitlab, and other solutions. I'm very happy overall, the interface is great. It's a bit slower than github currently (the web interface) as I'm using the online version rather than self hosted, but apart from that it's really bloody good. I'll be recommending it to others going forward and using it for all new rep…

Thanks, that's good to hear. We're working hard on making it faster, this release being a major milestone in that work. Last release, we started shipping a performance monitoring tool [0], to make it easier to see what exactly is slow. [0]: https://about.gitlab.com/2016/01/22/gitlab-8-4-released/

Yep, also see our 'Make GitLab.com fast again' issue https://gitlab.com/gitlab-com/operations/issues/42 for updates about performance.

Re: GitLab 8.5 released

#72
post #16
post #5

I've moved all my private repos to Gitlab based on the chat on here and other places recently RE Github, Gitlab, and other solutions. I'm very happy overall, the interface is great. It's a bit slower than github currently (the web interface) as I'm using the online version rather than self hosted, but apart from that it's really bloody good. I'll be recommending it to others going forward and using it for all new rep…

What procedures did you follow to move your private repos over? I have been using private, self hosted git for years now. Were you able to move things over and keep commit history? (since I guess that's the only feature I currently have.)

Apart from the other methods mentioned here (such as the import from the user interface http://doc.gitlab.com/ce/workflow/importing/README.html) is also an import rake task http://doc.gitlab.com/ce/raketasks/import.html for administrators.

Re: GitLab 8.5 released

#73
post #31

Earlier quoted context omitted.

If you import from GitHub, your issues, PRs, wiki and all code will be imported.

It would be really cool if GitHub stored issue, PR, and wiki information in the main Git repo. That way all of these things would be very easy to keep in sync across different services. I've had this idea for a while now. I wonder if it would be practical and if anyone has ever tried something like this.

That would be cool, we're discussing distributed code review and issues in https://gitlab.com/gitlab-org/gitlab-ce/issues/4084

Re: GitLab 8.5 released

#74
post #60

Was 8.5 able to address either of these? Large commits can't be viewed: https://gitlab.com/gitlab-org/gitlab-ce/issues/10785 Users created via LDAP login continue to count towards the user-count even if the LDAP account is deleted: https://gitlab.com/gitlab-org/gitlab-ce/issues/11844

Thanks for asking. For the first issue work is being done but we need more time https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2705

The second issue seems more like something that could become a feature request than a concrete proposal. Consider leaving a comment in the issue with your proposal.

Re: GitLab 8.5 released

#75
post #57

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.

Just so you know, we recommend a minimum of 2GB https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...

Re: GitLab 8.5 released

#76
post #65

Very easy upgrade from 8.4.3 to 8.5 on Ubuntu using the omnibus packages. I did have to install bundler in my system Ruby (I have RVM on the system; the install scripts executed via apt-get apparently doesn't care), but that was the only hiccup.

You should not have to install bundler on your system to upgrade to 8.5. If someone else encounters this please open an issue so we can diagnose the problem.

Re: GitLab 8.5 released

#77

We're super excited with GitLab 8.5. It's much faster, no matter the size of your instance (but especially for larger instances). The Todos, ability to revert commits and CNAME support for Pages, are things that have been much requested and we're happy to have now. As always, we're here if anyone has any questions about anything.

Hi Job, does this mean it is also faster in low memory environments like 512M? ToDo integration is a great feature!

Re: GitLab 8.5 released

#78
post #42
post #39

Still using redmine + gitolite here but have been watching Gitlab for a while, in fact I tried it yesterday and it's still quite resource hungry and slow(using DO's default installation with 1GB memory). Redmine+Gitolite has nearly everything I need but Gitlab's code view interface is better. Redmine's backend seems running more efficiently but its interface is not modern enough at this point, especially on how to re…

gitlabs minimum requirements are 2G of ram (although that's for 100 people). Without trying to appear as if I'm defending gitlab itself, I've always been of the notion of "Do it right and then do it fast". This is how postgresql is starting to beat the ever-loving crap out of mysql now, it used to be the slow option, now it's the one that wont eat your baby.

Thanks, we indeed recommend 2GB for all installations https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...

I've made it a bit more clear in https://gitlab.com/gitlab-org/gitlab-ce/commit/b31c68aa2afbb...

Re: GitLab 8.5 released

#79
Much faster! I notice it's rendering large source files instead of displaying them as binary now, so great!

One issue: I'm getting a really weird animation/hover over effect on the Gitlab icon in the upper left corner. Is that meant to happen? Is there a way to disable this.

Other than that, everyone should upgrade to this version.

Re: GitLab 8.5 released

#80

I'd love to try GitLab out, but the OSX installation instructions [1] are a bit of a put off. I'm not even sure if that's the right URL, but it's where google takes me. The instructions refer to a "runner"; I'm not really sure I understand what that is, and it's not explained anywhere. The "ci" makes me think this is something to do with continuous integration, so I'm really not sure if this is the right thing to be…

It's a waste of resources but you could run it in a vm with or without docker.
Post reply on HN