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

GitLab 8.5 released

about.gitlab.com

Post reply on HN
Print view View original

101–110 of 246 posts

Re: GitLab 8.5 released

#101

Post by jobvandervoort »

fsiefken wrote: post #80
oneeyedpigeon wrote: post #66

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.

Find the official Docker image here: https://hub.docker.com/r/gitlab/gitlab-ce/

Re: GitLab 8.5 released

#102

Post by cheald »

balameb wrote: post #98
cheald wrote: post #83

Earlier quoted context omitted.

Here's my console buffer from the installation: https://gist.github.com/cheald/6002dbe275a379a5f85a tl;dr: apt-get install gitlab-ce failed with "bundler not found". rvm use system; gem install bundler, apt-get install gitlab-ce and it worked fine.

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 in the active RVM environment, it works fine.

Re: GitLab 8.5 released

#103

Post by bronson »

746F7475 wrote: post #100
flashm wrote: 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…

I guess it's good if you just want private stuff, but if you want to build portfolio type thing or want discoverability private stuff isn't ideal

No problem, just click the "Public" radio button.

Re: GitLab 8.5 released

#104

Post by eknkc »

jobvandervoort wrote: post #12
d33 wrote: post #10

Two releases ago, updating was a bit of a pain for me, so I guess I'll wait until Friday with this one. Anyway, the new features sound really good!

What was painful exactly?

First upgrade for me (8.4 -> 8.5)

On a pretty small instance (1.7g ram google cloud) + 1gb disk swap the omninbus update failed with out of memory. Added some more swap space and it finished fine. It's probably not powerful enough to run it though.. Just a heads up.

Re: GitLab 8.5 released

#105

Post by sytse »

exstudent2 wrote: post #99
jobvandervoort wrote: post #97

Earlier quoted context omitted.

We're bringing the option to customise the interface to CE. If you run your own instance, you can replace the logo to disable it.

Thanks, will do. Looking forward to the interface customization options.

Great! Docs for the branded login page are at http://doc.gitlab.com/ee/customization/branded_login_page.ht...

The merge into CE is happening in https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 and hope it will be in one of the 8.5 patch releases.

Re: GitLab 8.5 released

#106

Post by jobvandervoort »

eknkc wrote: post #104
jobvandervoort wrote: post #12

Earlier quoted context omitted.

What was painful exactly?

First upgrade for me (8.4 -> 8.5) On a pretty small instance (1.7g ram google cloud) + 1gb disk swap the omninbus update failed with out of memory. Added some more swap space and it finished fine. It's probably not powerful enough to run it though.. Just a heads up.

I'm sorry to hear that. We advise a minimum of 2gb of ram, so I'd expect it run successful for you. I created an issue on the omnibus issue tracker about the memory requirement for upgrades, here: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1135

I'm glad you managed to solve it, though.

Re: GitLab 8.5 released

#107

Post by josteink »

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?

Re: GitLab 8.5 released

#108

Post by dudul »

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…

I can't tell if there is a real shift, I would say no. GitHub, in a lot of people, is synonymous to Git. GitLab is superior in a lot of ways, more feature, open source, very open as you pointed out. Their pricing model supports free private repos. Not sure what it would take to really make people reconsider GitHub as the default goto place to host OSS repos.

Re: GitLab 8.5 released

#109

Post by grokys »

iBotPeaches wrote: post #36
whitenoice wrote: post #30

Impressive release! Is there a guide on migrating from install from source to using omnibus? We currently upgrade from source but would like to move to omnibus.

Warning as someone who just did that. MySQL is EE only on Omnibus. I switched from Source (MySQL) to Omnibus only to find that MySQL was EE only. So I had to go back to Source.

We recently switched from a source package using MySQL to the omnibus package and the migration to Postgresql was really easy and went without a hitch.

Re: GitLab 8.5 released

#110

Post by dman »

Can i use dnf update on fedora to update the gitlab package if I have the repo installed? I am on fedora 23 and doing dnf update doesnt upgrade gitlab. Also doing a dnf install gitlab-ce gives me a message that gitlab-ce-8.2.0-ce.0.e17.x86_64 is already installed.
Post reply on HN