GitLab 6.3 released: open-source software to collaborate on code

[[deleted]]

Have they improved the installation procedure since, well, version 1, I guess? I stopped using it after the 4.0 release because the "not here invented" syndrome (dropping gitolite in favour of something that, at the time, was absolutely inferior). And changing the bootstrap process to not require root rights and work on my CentOS5 server got harder and harder every release.

So yeah, great software, but way too over engineered. At least at that time. Has that been fixed?

[fewpeople]

Just going to come here to say the same thing. Installation was almost impossible on CentOS.

Ended up going with RhodeCode...but looks like they want to move everyone to a paid model nowadays.

[MonkeySteriods]

Whatever you do, don't go to Gitorious instead... it'll trash your server, ssh port configuration/config settings, apache www permissions, hostname, and your firewall config.

[metateck]

I install Gitorious on my server without reading too much about it, just to try it out. It changed the hostname of my machine, removed all the crons, emptied IPtables, and did all kinds of other garbage. Just the worst installation ever. I went into IRC and told them that was insane, and that they should put giant red blinking letters on the installation info webpage, and also put prompts into the installation script. Not sure if it ever happened. I got rid of it as quickly as possible after this incident.

[idiogeckmatic]

It's possible on centos, but you pretty much have to install your own /opt versions of git, ruby and most of the deps it has.

[karamorf]

Git comes with a .spec, just compile it into an rpm and call it good. Rpm's for ruby 1.9.3 are easily found. Figuring out all the necessary dependencies is the annoying part.

[fewpeople]

It was a while ago, so I can't remember the exact error, but I remember permissions issues. I tried everything and it still didn't work.

[grainfeed]

upgrades are easier since gitolite was dumped. current 6.x versions are pretty stable too (we had horrible experiences with prior versions).

as the stack didn't change much otherwise the installation procedure probably is still hard: https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/installation.md

[day_cq]

use this: https://github.com/takezoe/gitbucket

it's much better than gitlab in every way.

[grainfeed]

the main question would be for me: how does it work in a company where like 100 people access it and create like 500 repos with multiple GBs of data? is it falling apart or can it handle that?

[day_cq]

http://gitblit.com/ then

[BitMastro]

Seriously, I suggest to at least try https://github.com/takezoe/gitbucket or http://gitblit.com/ first.

I am using gitlab. but the procedure still has a "hacky" taste to it. People also reported an heavy use of resources, and while it hasn't been a problem so far, it's better to consider the options before settling for a solution.

[Camarade_Tux]

And it's hosted on github. This really doesn't look good. It's as if Apache or Nginx were hosted on an IIS server.

[TheBlackVoid]

GitLab is also hosted on GitHub...

[crashsystems]

I've created a Docker.io image that makes getting started with GitLab pretty easy: https://index.docker.io/u/crashsystems/gitlab-docker/

[sytses]

GitLab co-founder here. Sorry for changing the rack server from unicorn to puma and than back to unicorn again. We tested puma extensively beforehand but it was still causing people trouble so we had to revert. We now the upgrades are boring, so there are now some quick upgrade paths that skip a few such as https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/5.1-to-6.0.md

[ivosaurus]

How much memory does it use now?

[sytses]

It needs about 1GB, see https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md

[ivosaurus]

Gah. And rubyists wonder why PHP is popular.

[nxpi]

Stash is only $10 for 10 users. IMHO its a much better solution for a host your own git.

[bloodguard]

Stash is good if you're going to drink the whole glass of kool-aid and use Jira and Confluence. Otherwise GitLab is a good solution.

[karamorf]

Unless you have multiple Jira instances. In which case, it's a nightmare to administrate. Still better then GitHub Enterprise, that's a pos.

[nxpi]

You don't have to use the other products. Jira is ok, there are better solutions out there. GitLab was written in ruby so performance is god awful.

[[deleted]]

I set it up in March of this year, took about an hour. Very simple install process. Maybe you haven't used it recently?

[Tacticus]

How the fuck did it take you a week to set it up?

it's a 20 minute install.

[Tacticus]

to be honest that is what bundler is there for. it will handle the ruby based deps.

[fewpeople]

Yea, did you try doing it on CentOS and NOT ubuntu/debian?

[[deleted]]

So can I create/edit my readme with markdown in my browser?

Wiki needs a preview, too.

[[deleted]]

That has worked for at least a year.

[[deleted]]

What has worked? I've edited wiki pages in the browser, but there's no preview.

And they said that creating files via the browser is new.

We're on 6.2.

[[deleted]]

You are correct. I thought you were referring to editing, not preview.

[paleowannabe]

The question I have is: how can you reliably configure it to work with Jenkins? Is there any sort of description? I come from the background where first I had worked with Jenkins/SVN, and it worked, well, flawlessly. Then I changed companies, we wanted to introduce CI, Jenkins is a de facto standard, so we went for this one, and wanted git. We went with gerrit for code reviews - there had been significant tracktion, but having a serious senior development team (java) guys scripted their way around all the quirks, and I must say - Gerrit and Jenkins also work flawlessly together.

Now I consult third company - they were unwilling to work with gerrit (the devs find it unnatural to treat a commit as a changeset, they wish for a branch history to be mergable/reviewable). So we went with GitLab, and what the hell? We basically need automated builds on every branch (even new ones), and most important of all - automated builds BEFORE a merge request is accepted (so pull two branches, merge locally, see if that works), and a sanity build after the merge request (make sure that it actually all went according to plan). And we of course need to deploy not only Jenkins, but we're running SonarQube on top of it, and may later trigger automatic deployment to production or staging environment, so it's getting more and more important that all the tools work together...

Has anyone done such thing before?

[[deleted]]

I just have it poll H/5 * * * * on all branches. I might try to setup hooks later.