GitLab 6.0 Released

http://blog.gitlab.org/gitlab-6-dot-0-released

by conductor • 13 years ago

168 88 13 years ago

blog.gitlab.org

X-Istence3• 13 years ago

We run this at work, switching from Gitorious actually, and so far everyone on the development teams has been really impressed. It is fast, works well, and the web interface provides everything we need, and more.

tsm3• 13 years ago

It's always annoyed and confused me that GitHub Enterprise exists. GitHub is founded on the premise that open source is a good idea...yet for self-hosted git management the freedom-friendly solution is...GitLab.

So good for GitLab for existing at all, and congratulations to the team for releasing v. 6.0! May there be many more!

nXqd• 13 years ago

still, the github is not open itself. And we cannot expect that since they have to earn money to keep running that amazing open source platform. Gitlab is great btw. Congrats

sytse22• 13 years ago

Thanks nXqd! (I'm a GitLab.com co-founder)

conductor• 13 years ago

Actually... This is a quote from the article:

"GitLab 6.0 will be the first release that will also be available in an Enterprise Edition, for more information please see the GitLab.com Blog [1]"

[1] http://www.gitlab.com/2013/08/22/introducing-gitlab-6-0-ente...

cbhl• 13 years ago

"Enterprise Edition" for LDAP groups sync?

I remember working on LDAP integration for a SaaS product four or five years ago... I'd say that is exactly the sort of feature I'd expect to delineate a consumer/enterprise edition on.

Plus, base LDAP support is still in the community edition. Sounds reasonable to me.

kylec• 13 years ago

The cost breakdown:

    * GitHub Enterprise: $5000 per 20 users per year, effectively $416.67
      per 20 users per month. (You have to pay yearly though)
    * GitLab Enterprise: $39.80 per 20 users per month, or $398 per
      20 users per year
    * GitLab Community: Free

Basically, GL Enterprise is roughly 1/12 the cost of GitHub when purchased yearly, and 1/10 the cost if paying month-to-month (which GitHub doesn't offer).

Interestingly, GitLab is taking a page from GitHub's book and requiring customers to purchase user packs in groups of 20.

darkstar999• 13 years ago

I'm confused. What's wrong with GitHub selling a product for enterprise? (HUB not LAB)

tsm3• 13 years ago

GitHub takes advantage of open source ideals to build its community...but doesn't open source its own software to give back to the community. It seems a little hypocritical.

I'd feel much better if GitHub had a useful open source core (like GitLab, or Chromium, or AOSP, or darwin, or...) and then had an Enterprise Edition that had enterprisey features (GitLab's LDAP integration is a great example) and professional support and such.

banachtarski2• 13 years ago

This is just silly.

tsm3• 13 years ago

Mind adding to the discussion by explaining how?

eddieroger• 13 years ago

Most of what that money buys you is the security and managerial comfort of SLAs and enterprise support. Community Editions scare the enterprise because when something breaks, there's no one on the hook to fix it (forgetting, of course, countless newsgroups, mailing lists and chat rooms usually dedicated to the topic). When GHE fails for some reason, your helpdesk can rest assured that within 4-24 hours (depending on SLA) you will have a fix that no one in the company is responsible for.

sytse22• 13 years ago

GitLab.com co-founder here. We have a subscriptions that has enterprise support for GitLab so we are on the hook to fix it.

shmageggy• 13 years ago

I wish they would spend a bit more time streamlining the installation procedure and/or streamlining dependencies. It looks like a great product, but attempting to get it set up left me with the feeling that it's extremely bloated. And 2-4Gb recommended RAM is... a lot. I know, I'm bitching about something that they are giving away for free, but oh well.

mitchty2• 13 years ago

Try not running it on ubuntu, or in a location that doesn't allow sudo to be setup to allow any command in quite the same way as the install docs assume.

I've a forked version of their startup script that doesn't use sudo for the init script (honestly wtf why is this so common redis does the same). sudo the init script don't sudo in init scripts. Meh, its not too bad I'm at the point of 15 minutes to upgrade between releases so its not too bad but yeah it isn't a trivial install.

sytse22• 13 years ago

Good to hear you managed to install without sudo. Does this mean you didn't create the git user? How did you solve the git@ urls for git over ssh connections? Did you use the init.d scripts?

MetaCosm3• 13 years ago

I guess it all depends on perspective. When I picked up Gitlab (18 months ago) -- the major competition was Gitorious -- which if you think Gitlab has a bad install -- you have no idea.

Gitorious _had_ (haven't looked at it recently, I guess they spent a lot of time addressing this) the worst install I have ever seen (any package, ever, 15+ year in the industry) ... it seemed built for complexity just to generate them consulting / professional support hours. Gitlab in comparison was blissfully simple.

As for the bloat... we have nearly 180 projects and 10+ user accounts, and while the baseline setup has a lot of bloat (I blame choice of language / framework) -- it generally works fairl well -- sometimes you have to kick Ruby.

jeremiep• 13 years ago

The installation pain can be largely removed by using chef.

InclinedPlane• 13 years ago

The really annoying part is upgrading. Which right now the instructions tell you to do bit by bit instead of whole hog. If you end up behind it makes it harder to catch up, which seems like a bad thing.

azmenthe• 13 years ago

I set this up for use at my previous firm and it was extremely difficult and that was 2 years ago (so version 1 or 2 I think).

It was great once it finally was up and running but I'd only recommend it if you have a legitimate intellectual property concern and can't use github enterprise.

sytse22• 13 years ago

GitLab.com co-founder here. Installation got a lot simpler since 5.0 when you no longer had to install gitolite as well. I hope your upgrade will be smooth.

Zren• 13 years ago

Try Bitnami's installer. http://bitnami.com/stack/gitlab

I have their VM iso running in a VBox Headless process and it idles at 44Mb. Mind you, it only get's minimal use.

mikewhy• 13 years ago

They continue to eschew using `foreman export` / `foreman run` / `bundle install --binstubs` in the docs, when it does simplify a lot of the installation / upgrade process. I've even sent pull requests that add capistrano / unattended deploy support that have gone nowhere.

I love the software, but the installation / upgrade docs are always hell compared to your average `git pull && bin/rake db:migrate && foreman export`.

Having said all that, I'm running it on an old box with 512MB of ran and it's tolerable.

sytse22• 13 years ago

GitLab.com co-founder here. Thank you for the suggestions. There is a proposal in the core team to switch to --binstubs. We will also move the run logic from init.d to the bin directory so you can also use it with monit/god/bluepill/omnibus/chef/foreman.

616c• 13 years ago

If bloat is a concern, I used to use gitweb (which is Perl) over CGI on a sharer server and performed very well for my uses. All I had to do was write a short shell script to create the repo on the server, and SSH was running for me anyway (especially if I was going to push-pull).

Now I use cgit, and discovered it a while before the Linux kernel did. [0] It is crazy fast (CGI written in C! Can you believe the nads on those guys?) and will be portable anywhere C is.

If only I could get git's smart HTTP working, but I could not find much on the internet to clue me in. Still pretty cool.

[0] http://comments.gmane.org/gmane.linux.kernel/1450151

sytse22• 13 years ago

We're working hard on streamlining the installation but for now the focus is on a reliable installation method for most situations. The recommended RAM is 1GB, see https://github.com/gitlabhq/gitlabhq/blob/master/doc/install... (I'm a GitLab.com co-founder)

binderbizingdos2• 13 years ago

Thanks for creating Gitlab. It helped us a lot internally. We were using plain Gitosis before. Now nobody gives a hoot about that anymore :)

My only request would be to focus more on stability. We run it for 1 year now and there were many problems with upgrades and various changing issues with the different versions.

So for us less new features but a better tested Gitlab would be great. Maybe some kind of "stable" release? Not sure...

dfc• 13 years ago

The most streamlined installation is "apt-get install gitlab." ;) What happened with the ITP for an official debian package? All of a sudden it seemed like it ran out of steam in February.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700630

johnsea• 13 years ago

If you have problems with the installation use the free cloud service - nothing to setup. Or use vagrant (didn't try out myself).

It is a great product and 'my' users love it (finally convinced them to move on from svn). One can copy-paste the instructions, it's rather lengthy but never had problems.

It's wonderful what GitLab gives, thanks a lot!!

FooBarWidget• 13 years ago

I don't know why they recommend 2-4 GB RAM, but we're running Gitlab on 512 MB with Phusion Passenger Enterprise just fine. It also helps that Phusion Passenger Enterprise happens to use the least memory among all Ruby app servers.

sytse22• 13 years ago

Good to hear 512MB works too. The recommended size is 1GB, see https://github.com/gitlabhq/gitlabhq/blob/master/doc/install...

Keyframe• 13 years ago

Turnkeylinux has a prepared image with it http://www.turnkeylinux.org/gitlab

neumann• 13 years ago

I coaxed the team at uni over to git by installing Gitlab. The ease of a web interface to view the repositories impressed even those academics who version control by copy and pasting folders of their code and adding a '_works' suffix. It also allows the SVN users to start using git as it was based on a client-server model.

The gem dependencies are incredibly large, but I found the install process well documented.

MetaCosm3• 13 years ago

And generally the upgrade blog posts are dead on (cut & paste to do your upgrades).

simlevesque2• 13 years ago

It's silly but the thing I miss in Gitlab is that you can't use tables in Gitlab flavored Markdown.

roryokane• 13 years ago

Have you tried using `<table>` tags? Standard Markdown allows you to write arbitrary HTML tags in your text. I used it recently to write a table in a GitHub issue comment.

If GitLab doesn’t even allow you to use `<table>` tags, that’s probably not a problem with their Markdown flavor, but a problem with the sanitization step that runs after the Markdown compilation. Unless GitLab is using a broken implementation of Markdown that doesn’t allow any inline tags.

simlevesque2• 13 years ago

It is the case, Gitlab flavored Markdown strips inline html.

overshard3• 13 years ago

Every time I see a new GitLab release I get excited to install it. Then I see the install instructions and immediately give up. The number one thing GitLab needs is an easier way to get it setup.

wickchuck• 13 years ago

If you've dealt wih servers and played with rails it should be pretty trivial for you to set up gitlab. Remember it's open source so before you say it's too hard there are paid alternatives that have one click installers. Gitlab is a fantastic project and it would be worth the time getting it installed.

overshard3• 13 years ago

GitLab is a fantastic project and it is open source but that needs to stop being an excuse for how terrible an install process it has. It wouldn't be a problem or me to install it but it is a huge barrier for many people using it.

Nican• 13 years ago

Taking a look at the installation process, and it is pretty much trivial, but long. The developers could try creating an apt-get package for even simpler installation.

overshard3• 13 years ago

Yep, I'm actually making one and a dockerfile for it as we speak just so that I can deploy it myself easier. I may make it public.

X-Istence3• 13 years ago

The install instructions are incredibly simple. As long as you follow the instructions it is set up in less than 30 minutes...

Diederich• 13 years ago

I would not call them "incredibly simple", but I have also gotten gitlab going in about half an hour, twice.

chii• 13 years ago

to a non-sophisticated user, following instructions (which they may or may not understand the reasons for) instead just running a single executable is complicated.

sytse22• 13 years ago

GitLab.com co-founder here. Thank you for commenting. We're looking into packaging but this will take some time. Maybe you can try the Bitnami images (http://bitnami.com/stack/gitlab), they are already upgraded to 6.0.

anonymousDan• 13 years ago

Hey sytse, Is there any downside to using the bitnami images?

dbalan• 13 years ago

Ironic is gitlab using github for development, reminds early days of GNU running their infrastructure on UNIX.

Rovanion• 13 years ago

They do use their own Gitlab installation for internal development. But they serve different purposes. Gitlab is used by developers accustomed to the project and Github to get new developers in.

sytse22• 13 years ago

GitLab.com co-founder here. Thanks for explaining Rovanion.

senthilnayagam• 13 years ago

do you think a vagrant or docker image can make it popular?

fsiefken• 13 years ago

actually there appear to be vagrant and docker images already: https://github.com/gitlabhq/gitlab-vagrant-vm https://github.com/crashsystems/gitlab-docker

bdcravens• 13 years ago

The Vagrant image appears to be using Vagrant 1.0.X, as it requires password for NFS shares on OSX, something not required in 1.1+

ridruejo• 13 years ago

Why not use BitNami pre-configured VMs? http://bitnami.com/stack/gitlab

Rygu• 13 years ago

We use Atlassian Stash at work after having tried a bunch of different git review & merge tools, including Phabricator, GitLab, Gerrit and more. Atlassian's Stash provides the best code review tools like per file diff + commenting. GitLab was our second choice but unfortunately it doesn't handle bigger diffs (feature braches etc) well. Maybe if a GitLab-dev is reading this, we need per file reviews! (And better notification settings!)

sytse22• 13 years ago

GitLab.com co-founder / GitLab core team member here. Thanks for detailing your needs. Many people use GitLab merge requests to do large code reviews for feature branches. These can be up to 100 commits and include per file diffs with line commenting. How many commits are your feature branches? We now have notification settings per project and mentions in issues and merge requests, would you want anythings else regarding notifications?

kriro• 13 years ago

"Today we present a new major GitLab version. There are a lot of improvements to make GitLab even more awesome."

I think the first sentence of every new release should at least explain what GitLab is. A new version of GitLab the tool for X,Y,Z. Some people will see a link to it in their tech news source of choice and think "oh that's interesting, let's check what it is"

Keep up the good work :D

sytse22• 13 years ago

Thank you for the suggestion, will try to remember during the next release.

ksec• 13 years ago

Um... I dont get it.

So they release a GitLab Enterprise Version. And Killed off GitLab Cloud? Well not actually killing it but offering it for free.

Why?

What's the business case behind it? Or GitLab simply dont want to run a Commercial, High quality Code Hosting Services?

Without some sort of payment, I think any business will be hesitant to use GitLab Cloud.

sytse22• 13 years ago

GitLab Cloud gets our full attention. We just discovered that the majority of our income is from on-premises installations and generate revenue from that. Many of our now subscribers started with Cloud so we'll make sure to provide a great service.

ausjke• 13 years ago

Tried a few Gitlab versions, stick with Redmine for now, though I do hope Ubuntu to support newer Redmine versions, which should not be too hard, but most plugins are not catching up with newer core releases.

inthewind• 13 years ago

Sorry, but why would I want gitlab? And what are the alternatives?

sytse22• 13 years ago

GitLab is used to collaborate on software. It uses git repositories and has an issue tracker. (GitLab.com co-founder)

GitLab 6.0 Released

Related Stories