GitLab – Open Source Git Management Software
gitlab.com
gitlab.com
Long time ago we also assessed GitLab and found it usable but not quite there yet for production use. Though it looks nicer now.
Plus the ability to prevent pull requests from being merged without X approvals, at least one successful Bamboo build etc. It's all very well integrated and polished.
I'm just waiting on rebase instead of merge for pull requests.
I wish it allowed comments in more places than just PRs, but it's been pretty great so far.
I'd still like to see cleaner Jira integration.
Reading code through Stash is quite nice as well, much faster then bitbucket.
Gitlab seems to be improving at a crazy pace, which we hope to make the switch to soon.
I couldn't face Stash after that.
Edit: Atlassian support are excellent but we have to bug them too often with entire sites down (workflow consistency issues fucking the entire JIRA instance which happens at least once a month) for the product to be considered quality.
Hey anything is better than SVN which is what we use now!
Give it a try!
On the user side it hits all of the big items and the interface is useable. It doesn't have some features like GitHub's image diff or gh_pages support, but for many things there are Stash plugins that either exists or you can write. And they provide an easy way to not leak internal url's while using gravatar (http://benjamin-meyer.blogspot.com/2014/03/how-to-stop-leaki...)
The biggest downside I have at this point would be that out of the box the permissions model is not as rich/robust as gitolite. Although most Git frontend servers are no where near as rich as gitolite.
Edit: Well, sorta. It sounds like Atlassian bought BitBucket but ended up rewriting it as a standalone product (instead of SaaS).
Anyone can add their favorite apps and promote them.
(I'm not affiliated with Bitnami, and greatly appreciate the service they provide)
This will make GitLab an easier choice in the future. If you're looking for a lighter choice Gitbucket is really nice: https://github.com/takezoe/gitbucket
I know Ruby relatively well but I'm by no means a "pro", and I had no issues.
The problem I've been having is when I go to a commit, in Github I'll be able to see what's changed (the diffs), but in Gitlab I often get "diff too big and not shown for perf reasons" or suchlike. This inability to reliably view diffs makes me wonder how we're going to do code review on projects hosted on Gitlab.
Does anyone else have experience with this, or any workarounds?
The example I had from this morning was quite a large diff (47 changed files). I'd rather have a large page load time and be able to see the diffs though.
Thanks for the suggestion. :)
1. You can no longer assign a MR to someone at the time of creation.
2. The CSS looks broken. https://github.com/gitlabhq/gitlabhq/issues/6842
3. Successful MR's no longer turn green. There is no quick visual feedback, it used to go green.
My team and I hate the new "improvements", but appreciate the work.
Does anyone else feel this way?
I recently toyed around with InfluxDB which is a similar thing (written in go, no external dependencies) and it was pretty novel to have a 'self contained' binary like that.
I suspect it's especially helpful when dealing with docker images as well.
This is not true. It aims at being a great git web ui and management system first and foremost.
``Since we choose to use pure Go implementation of Git manipulation, Gogs certainly supports ALL platforms that Go supports, including Linux, Mac OS X, and Windows with ZERO dependency.
More importantly, Gogs only needs one binary to setup your own project hosting on the fly!``
But even if "all it aimed" was to be a duplicate in another language, that's just part of what will define it in the future. Linus didn't "aim" for his "just a hobby, won’t be big" project to take over the world and it did. Public open source projects have some of the most unpredictable paths - I'm not sure why you're trying to imply this one's an exception and it'll go nowhere!
... and you know there are 0 security vulnerabilities you don't know about in Go Lang or GoG, and it's 100% now and forever ?
... you know you can run any rails app using a localhost webserver ... just saying.
Gitblit is in another universe in terms of ease of installation, upgrade and maintenance, and very close on features. Even with a .deb package for Gitlab, my upgrade experience with previous versions wouldn't make me leave Gitblit. It's just dead simple.
The biggest reason for moving from GitHub to GitLab was not having to worry about additional cost for creating new projects (we have hundreds of projects and most of them are rarely accessed long after they were created).
It's also neat that we have the ability to customize GitLab if we wanted to, e.g. in 2012 we ran some experiments to create projects from templates directly in the GitLab interface [1]
And lastly, since we're not in an environment with six-digit numbers of users and constant DDOS attacks - we're able to keep a much better uptime than we had before with GitHub.
[1] http://enga.ge/development/creating-a-sturdy-deployment-work...
We also use Atlassian Stash and JIRA for a client project (the client migrated from CVS to git) and honestly, found it to be quite similar in functionality and not too much better for the extra costs. Mostly, it helps that both (Stash and JIRA) are linked together, but I'm sure that can be done with GitLab and another issue tracking software like Bugzilla.
After I fixed that, I disabled the bundled nginx so I could instead use the system's nginx. I had to modify the chef configuration scripts to change directory permissions so the www-data nginx could read the git-owned socket.
I'm very happy now that I got it working! My only nitpick (aside from some installation frustrations) is that the syntax highlighting for large files can be very slow. Does anyone have any tips for that?
One thing I’m curious about is performance, as with a personal project I found the `grit` git-ruby bindings rather sluggish when loading in multiple repos… The new `rugged` bindings are supposed to perform much better and if I understand in time Gitlab will switch to them.
Whilst we like using it, the UI doesn't always feel intuitive and has changed a lot over the last few versions, 6.8.0 feels worse to us — mainly due to the weird Merge Request UI changes. https://github.com/gitlabhq/gitlabhq/issues/6842
Still, I personally prefer the look and feel of GitHub. But it's a good free solution and we're really grateful for the work people put into it.
I switched to Gitweb and sd (http://syncwith.us/sd/using/). I don't love sd, but the overhead of managing source and tickets for myself makes the combo worth it.
Looks like the vm is not the latest version but it was a painless install.
Big fan of it.
I use Gitlab, Graylog, Nexus... anything I'm missing out on?
http://gitsense.com/blog/features/programmable-metadata/
I wouldn't download the current beta version though. I'm currently testing a newer version with some enhancements which should be available for download by tomorrow.
http://www.elasticsearch.org/overview/kibana/
What about CI (builds)? There's a lot of options here, but Jenkins is pretty good. It's a bit of a hack, but I sometimes use it as a quick way to put a frontend on a shell script. The build history is an audit log and the job config history tracks changes to the script.
I could see us using GitHub further down the road after we get some best practices in place and start using Git more, but for the time being GitLab is an excellent way to test the waters, especially since the GitHub Windows and Mac apps will work with an arbitrary 'origin' URL.
You might trust US companies, but after Snowden many people don't trust the US anymore (industry espionage). And there is no reason if you aren't a one man shop to not host such things yourself.
I'd imagine the main reason to go with GitLab is that it's free. GitHub Enterprise costs more than Stash (although it offers more).
I know that there is some payed service that isn't self hosted.