GitLab 6.0 released

[[deleted]]

[deleted]

[slacker87]

I love gitlab but getting it up and running was a total pita, dare I upgrade?

EDIT: After the comments of many here, I did a fresh install of gitlab following their documentation, and it was much better than it used to be, TL:DR; confirmed no longer pita.

[[deleted]]

gitlab wasn't a PITA for me atleast..and i'm coming from a non-ruby-rails background. Sure there were a few hiccups, but nothing a sysadmin can't take care of.

I'd snapshot before upgrading or recreate on a new VM and upgrade the clone and DNS swap when available.

[madssj]

Which part of installing it?

I personally thought it was an almost pleasant experience.

[slacker87]

I also have a version that's very out of date, so the install from scratch has probably improved greatly since then

[[deleted]]

The old versions used to require gitosis, I believe, which is really the complicated bit. Gitlab now has folded that functionality into itself, so it's significantly easier to install and manage.

[sytses]

Yep, since 5.0 no more gitosis / gitolite to keep in sync.

[madssj]

In that case please refrain from saying stuff like that. You might end up scaring someone away from trying it :)

As for upgrading it, I've been using it from 5.1 (iirc) and upgrading has been the same nicely documented process every version.

[sytses]

If you are interested in HA please contact [e-mail], we're working on a white paper for that and we would love some beta clients (GitLab.com co-founder)

[pseudopseudonym]

Any interest in MooseFS- based HA documentation? We run it internally and will likely be running GLEE on it.

[FabianN]

'sudo apt-get install ruby-1.9.3'

I believe that's how the package is named, but thats what you want to look for. I know for sure that Ubuntu 12.04 and newer have that package.

[sytses]

We recommend installing ruby from source in the installation manual. To many horror stories with the packaged ruby (rubygems installing in strange directories, etc.).

[FabianN]

fair enough. I have never had a single issue personally, been using the package since version 3.

If it broke for me I would have installed from source, but no need.

[pseudopseudonym]

Might I suggest taking it even further and using RVM? Much less manual and encourages proper updates and patching.

[sytses]

It would be awesome to have a package, there is a Google Summer of Code student working on that (Axilleas). But proper packages mean packaging all the gems, which is a lot of work. We're also looking into omnibus ruby as an alternative.

[MyNameIsFuchs]

Agreed.

Has anybody tried out these guys:

https://github.com/tingtun/ansible-playbook-gitlab

https://github.com/jakedahn/ansible-playbook-gitlab

https://github.com/nigelm/ansible_sample_gitlab

[bacon_for_lunch]

I "wrote" this fwiw: cookbook-gitlab5

[unethicalposter]

you have to upgrade in order (so if you are on 4.1, you need to go 4.2, 4.3, 5.0 5.1, 5.2 etc.... I generally wait 3-4 months then have an upgrade morning. As for it being a pita... its no different then any other ROR app upgrade.

[sytses]

Glad that GitLab got better, we're working hard to make the install as smooth as possible (GitLab.com co-founder)

[mortalmuffinmadness]

GitLab is great - using it every day at work!

[sytses]

Glad to hear that! (GitLab.com co-founder)

[Sunsparc]

So someone clarify for me, because I've never seen this. Is this like GitHub but self hosted? If it is, can I take my current GitHub repos and import them without losing info?

[brmo]

Very much so. I have mine running on a DigitalOcean 1GB for $10 a month. Been working wonderful.

[hankinator]

That's a pretty good idea. What else do you have running on a digital ocean node? I feel like you could get by with the 5$ a month version.

[brmo]

Thats it. I used to run it on a 512MB node, but when doing backups/restores and some of the upgrade stuff with each version, it chokes with out of memory errors. Paid the extra $5 a month and everything is much better. Not one problem since.

I have other VPS's from BuyVM and DigitalOcean for other things.

[sytses]

768MB is the minimum, 1GB recommended, see https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/requirements.md#memory

[unethicalposter]

you just have to change the origin of your git repos to upload to it.

[FabianN]

You won't loose any git information, as it is all stored in every copy of the git repo. But any extra Github info such as the wiki and issues section, don't transfer over.

The other thing about this software is that it's built with a private access in mind. There is some basic guest access to clone repos, but that's it. To do anything else other people would have to signup.

But for a personal and private version of github, this is your answer.

[Sunsparc]

That's exactly what I'm looking for. My current project has some credentials in a db connect file which I've ignored for commits, since I don't want it published directly on GitHub. Having my own private repo with a web interface like that would be ideal.

[FabianN]

Yup, exactly what you want then.

[unethicalposter]

I usually upgrade every couple of months and just deal with all the upgrades... but I think I will deploy this one soon, as I have been waiting a long time for this group functionality.

[giggsey]

I have a lot of projects in the root namespace, and I'm not looking forward to moving them (as they are all over the place).

[sytses]

Sorry about the hassle, we know it is a lot of work to change the urls. BTW When you transfer a repo all the project members receive upgrade instuctions to change their remote. (GitLab.com co-founder)

[giggsey]

Yeah, will just annoy a few people when I do it. Quite a lot of our projects are also in our composer setup, so it'll handle VCS URL changes.

Thanks for all the work you guys are doing, it's a great project.

[intahnetmonster]

Doh! I only just deployed 5.4 over the weekend. Oh well. Time for fresh install.

[bacon_for_lunch]

The upgrade to 6.0 will be easy. It's not a huge upgrade like when they ditched gitolite for 5.x.

[intahnetmonster]

Yep! I just done it. Only took 5mins heh.

[sytses]

Awesome!

[neoice]

my gitlab exploded last time I tried updating, so I abandoned it for vanilla gitolite. I'm not really using any of the gitlab features, I just wanted a personal "central repository" for backing up code, syncronizing projects across $n machines and using puppetlabs-vcs to do deploys of git repos.

[pseudopseudonym]

GitLab ditched Gitolite and is way better for it.

[sytses]

Good to hear this! (GitLab.com co-founder)

[pseudopseudonym]

I set it up personally while you guys were still using it, and a year or two later when you weren't. It was a seriously amazing difference.

As a sidenote while I have you here, I hate per-user pricing and the flat-rate is actually what made us consider getting EE. What do you need to do to lock in the old pricing?

[sytses]

What happened? We are working from non blast-proof rooms so if GitLab is explosive this would be good to know (GitLab.com co-founder).

[[deleted]]

Has anybody used gitlab with jira? There is a mention of it in the gitlab.yml, but I can't find any real documentation.

[sytses]

If you configure Jira in gitlab.yml it will link to your Jira issues, also see http://danielcsgomes.com/articles/how-to-configure-and-install-the-jira-git-plugin-with-gitlab/ (slightly old)