I've been using Gitlab to manage all my personal projects and I am grateful of how many features and constant improvements I get for free. Lots of free software have terrible UIs, eg. ReviewBoard, Jenkins, Graphite etc (these are great projects btw, just the UIs still look like from 2000). But Gitlab's UI is modern, elegant, and shows me all the activities on my projects. So I check my projects regularly and feel encouraged to work on them. Granted I can't tell if it scales for big teams but it is not an issue because I only share the instance with a few friends.
It has ran worry-free for me for almost two years besides occasional updates because I wanted the latest UIs and it helped me focus on coding. Thanks for the great work!
And we're spending more time to polish the UX to make sure it looks good.
GitLab is now one of the core products in our business and we (Devs, Ops and PM's) love it.
For Ops: * It's easy to deploy.
* It's easy to manage / support.
* Gitlab-CI now builds all our Docker images which is great.
* Gitlab-CI runners are a pain in the ass to deploy.
For Devs:
* It's workflow and code review is great.
* GitLab CI is a great alternative to using external CI systems / Jenkins.
For Everyone:
* It's wiki is great (and getting better over time).
* It's fast.
* It's very reliable.
* The community is great as is GitLab as a company.
* GitLab's momentum of the last 6 months has been great and shows no sign of slowing.
We don't have it hosted on very powerful hardware but it flies - so much faster than using Github, or our old internal setup of Gitolite+Gitweb/Redmine
I tried out Gogs yesterday and this is what I took away:
* It's incredibly fast.
* It's incredibly lightweight.
* At first it looks 'pretty' but quickly you it becomes clear that it's actually quite unintuitive to use (for example, it took everyone that tried it here longer than it should to find how to log a new issue).
* There is no wiki.
* There is no CI.
* There is no Debian package which would be nice.
* It's written in a language that most Devs / Ops can't contribute to or bug fix.
All and all, I'm very excited about Gogs for my personal git hosting at home / on my VPS' - but I don't think it's even close to providing the system that GitLab has at present.
> * There is no Debian package which would be nice.
True. AFAIK there aren't any packages in Debian that depend on go/golang yet, not even in sid. That doesn't mean one can't make out-of-band debs, of course, but gogs unfortunately isn't alone here. Does anyone know of any util/tool/package in go (other than golang) that's packaged for Debian?
> * It's written in a language that most Devs / Ops can't contribute to or bug fix.
As opposed to what? I'd think being able to patch something in go would be within the grasp of most Ops, and also most devs?
To clarify I didn't mean that it would be nice to have packages that are maintained by or in the default Debian repo - but an apt repo for the project would be nice.
I've found Go a pain to read and hack with - Ruby and Python however are a lot more readable and any of our ops or devs would feel confident in finding / reporting bugs in either.
http://gogs.io/docs/installation/install_from_packages.md
(Linked from the github page). So there are debs available of gogs. Trying to figure out how to build a deb from the git repo, but if all you want is upstream binary debs, you appear to be covered.
http://stackoverflow.com/questions/15104089/packaging-golang...
packager.io (which upstream googs uses) seems to be a nice way to just get packages out there, but as far as I can tell it's pretty well walled-off behind a service, so no easy way to build locally, off-line, or without using packager.io etc. In that sense it strikes me as a poor choice for Free software, as there is no promise that things will continue to work, or can be made to work, long term.
Actually, come to think of it... might be time to have a look at apt-get source docker.io...
http://blogs.msdn.com/b/oldnewthing/archive/2015/03/10/10598...
Nice to hear you're working on something simpler than simple. :-)
i hope someone who has the time and the skills forks gitlab and merges push requests of new features, even if they are already implemented in your pay-for version.
Seems like you sad exactly that a while ago:
"We are unlikely to merge this functionality in CE because there already is a nice implementation in EE."¹
It's your repo. You can do whatever you want with it, no need to merge PR for features that are already in your EE edition. That's why I hope someone forks it, or something better comes around.
¹https://github.com/gitlabhq/gitlabhq/pull/6883#issuecomment-...
We where unlikely to merge it because the code quality was low, if someone makes a good implementation we're more open to merging it.
BTW The pull request in question uses the git hooks to do code linting. I think it is a better user experience to do this in GitLab CI in parallel with the rest of your tests https://about.gitlab.com/gitlab-ci/
Oh, so it's not because "there already is a nice implementation in EE." Ok.
It's also in disagreement with what you sad on the EE announcement:
"If the community develops code for a feature that is already in EE we will certainly consider merging it or open sourcing the EE feature. This depends on several factors including the seriousness of the merge request, the number of GitLab users requesting this feature and if the feature is useful for small and medium size organizations."¹
For at least this particular feature the community is clearly interested (just by looking at the +1 on the github issue), but you continue to handle the CE version as "demo" software for EE. Which is ok. Just say so clearly.
¹https://about.gitlab.com/2013/07/22/announcing-gitlab-enterp...
The CE version is not demo or crippleware. It is a fully functioning version of GitLab without any restrictions that is just as performant and secure as the EE version. The only difference is that the EE version has more features.
That they said "there already is a nice implementation in EE" doesn't automatically mean they also intended it to remain EE-specific forever.
It could be also be read as "we won't merge this in the free edition, as we already have a nice implementation in EE we might merge later".
I also noticed that the current instructions were not very copy-paste friendly and made some small changes to remedy that https://gitlab.com/gitlab-org/omnibus-gitlab/commit/51d51fe1...
Do you have any plans for decreasing the resource footprint. I think the OP has a strong point in stating that it is a bit of a RAM drainer.
Could you maybe stop shouting GITLAB! all over this thread that's not about Gitlab?
I mean, if only every CEO was connected enough to read like almost every comment or criticism about their product online...
[1] https://github.com/kandanapp/kandan/ [2] http://feedback.gitlab.com/forums/176466-general/suggestions...
http://feedback.gitlab.com/forums/176466-general/suggestions... is marked accepting merge requests, we would love to see this too
Besides that, GitLab is fantastic and I thank you for that.
Upgrading GitLab is as simple as:
And we're working very hard to make sure this is a flawless, uneventful & boring process for 100% of the users https://twitter.com/PentiumBug/status/569930640725946368 We're also working on a package server so you can just use apt-get to upgrade.