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

GitLab 8.15 Released

about.gitlab.com

Post reply on HN
Print view View original

81–90 of 117 posts

Re: GitLab 8.15 Released

#81

Post by mikekchar »

connorshea wrote: post #28
Walkman wrote: post #27

This is nice and all but what about page load times? It can have all the bells and whistles but if you have to wait a minute for just one page to load, it's unusable.

We've spent quite a bit of time this year improving performance, GitLab.com is still slower than it should be but it's a lot better now than it was in January. Self-hosted instances that meet the recommended specs are already fairly performant, though we're always working to improve things regardless. As mentioned in the blog post, this release we decreased page size a lot (from 1800kb to 718kb for a given Merge Requ…

This probably sounds like a strange comment/question, but one of the reasons I haven't moved over to gitlab is that I know that it is unlikely that I will every be a paying customer. I actually don't mind that much about the performance issues (because I really just want cloudy git storage), but I don't like to take something for free unless I know the person giving it really wants to give it...

So as strange as it sounds, are you happy with people like me moving to GitLab even though it may compound your performance problems?

Re: GitLab 8.15 Released

#83

Post by sytse »

contingencies wrote: post #78
sytse wrote: post #62

Earlier quoted context omitted.

The image Cidan referred to was last pushed 5 hours ago when we released 8.15 and should always be up to date. For more information about our official docker images see https://docs.gitlab.com/omnibus/docker/README.html I've added a section to say that these images are officially supported with https://gitlab.com/gitlab-org/omnibus-gitlab/commit/26501d91... If you experience problems with them please feel free to fil…

should always be up to date OK. I definitely remember running in to something that looked official but wasn't up to date (remotely) a few weeks ago. Perhaps it was this image, perhaps not. IIRC at the time I was judging only from the 'updated [time periods] ago' data in the docker hub webpages.

Mmm, I remember mishaps with updating but those were quite some time ago.

Anyway, if there is an urgent problem with those consider tweeting to @gitlabstatus to get our attention. I think it won't be needed since many people use them so we should be on top of them. The only package that is sometimes late is the non-docker package for the Raspberry Pi since it takes hours to build.

Re: GitLab 8.15 Released

#84

Post by sytse »

mrmondo wrote: post #67

Plan meets final execution, love it guys and gals, great work yet again, we upgraded today without a hitch, within 30 minutes I had devs making positive comments in chat about the upgrade. Thank you again for all your hard work and the passion that drives that.

Thanks for leaving a comment Sam. Glad to hear the upgrade went smooth and people are happy. People that experience problems are more likely to let us know about it so we greatly appreciate your comment.

Re: GitLab 8.15 Released

#85

Post by ksec »

This may be a silly question. How did Github manage to burn 66M a year while Gitlab manage to be open source, offer an Free GitLab.com Hosting and continue a Rapid pace of improvement in multiple domain?

Re: GitLab 8.15 Released

#86

Post by jsrjenkins »

ksec wrote: post #85

This may be a silly question. How did Github manage to burn 66M a year while Gitlab manage to be open source, offer an Free GitLab.com Hosting and continue a Rapid pace of improvement in multiple domain?

Probably by concentrating more on the product than on politics.

Re: GitLab 8.15 Released

#88

Post by sytse »

anhtran wrote: post #87

Gitlab has too many downtimes for upgrading. When I got a failed push I was saying: Oh gitlab has a new version... :meh:

The downtime for upgrading is annoying. We're trying to get to a point where the database migrations don't require downtime. But the deploy of 8.15 caused 40 minutes of downtime, this is not acceptable. For the post-mortem please see https://dev.gitlab.org/gitlab/organization/issues/1082

Re: GitLab 8.15 Released

#89

Post by corobo »

softinio wrote: post #32
kaishiro wrote: post #31

Earlier quoted context omitted.

I'm curious what kind of spam you were receiving. I'm not sure I've ever received unsolicited email from them.

Marketing stuff. And I am not against them marketing their features but it should have had an unsubscribe button and sent in moderation in my opinion. Interesting that I get downvoted for giving honest feedback. I would have thought it would help them improve seeing how different marketing ideas impact their users.

> Interesting that I get downvoted for giving honest feedback

My hunch is the "GitHub is great" line, it feels a bit unnecessary and somewhat shill-y.

Re: GitLab 8.15 Released

#90

Post by supergreg »

AaronFriel wrote: post #55
contingencies wrote: post #25

Earlier quoted context omitted.

Even if I trusted it not to munge other things (doubtful), IIRC omnibus does not support my distro (Gentoo), and setting up another distro I have to (remember to) maintain just to support one application does not appeal medium term versus using a popular docker image which has done that for me already in a pre-tested fashion and should handle maintenance smoother. Basically I'm at this point: 'what's the easiest self…

I don't think your concerns are founded, I just deployed GitLab for personal use on a virtual machine with the omnibus image (gitlab-ce:latest) and it worked flawlessly. And since they released an update today, to upgrade all I had to do was: docker pull gitlab/gitlab-ce:latest docker stop gitlab docker rename gitlab gitlab-old docker run --detach --publish 60100:80 --publish 58432:22 --name gitlab --restart always \…

I tried the docker image for gitlab-ce just 2 days ago and had to exec bash into it and chmod a workhorse socket file to get it working. Glad they fixed it.
Post reply on HN