When comparing GitLab vs Phabricator, the Slant community recommends GitLab for most people. In the question“What are the best self-hosted web-based Git repository managers?” GitLab is ranked 1st while Phabricator is ranked 4th. The most important reason people chose GitLab is:
GitLab is a free and open source project licensed under MIT. Source code for Enterprise Edition can be found [here](https://gitlab.com/gitlab-org/gitlab-ee) and Community Edition [here](https://gitlab.com/gitlab-org/gitlab-ce).
Ranked in these QuestionsQuestion Ranking
Pro Regular updates
GitLab is being constantly worked on and has a new release every month on the 22nd. Updating is also very easy through a single apt-get command.
Pro Good web UI
GitLab's UI is clean and intuitive. Each view is designed to not fill the screen with useless information.
It displays the activity in a feed-type way in the most prominent part of the view. On top of that, there's a toolbar with buttons which can filter this feed by pushes, merge events or comments.
On the left, there's a menu that displays all the links that take you to the different views. For example, a file directory which displays all the files in that repo, a commit view which displays all the commits in cronological order, a network and a graph view that display important information graphically etc...
All these details make GitLab's UI extremely intuitive and easy to use, no view is overflown with information and every view displays only the most useful and crucial information needed at that time.
Pro Has wikis and pages
Wiki and pages support out of the box.
Pro Supports pull requests
Has pull request (AKA, merge request) support.
Pro Comes with integrated CI/CD solution
GitLab CI makes it easy to set up CI and deployment for projects in GitLab. It supports parallel testing, multiple platforms, Docker containers and streaming build logs.
Pro Easy to install with the packages
With the packages available here, GitLab can be installed in two minutes.
Pro Support for protected branches
A protected master branch means that no code can be merged to master without passing a code review by an authorised developer. With GitLab this comes out of the box.
Pro Permissions and roles are supported
It has private/public repositories, roles for users (master, developer, reporter, guest). All of these can be set from the user interface. Same permissions set for the UI work for the SSH as well.
Pro Issue tracking support
Has issue tracking out of the box. Creating tickets, commenting on issues, closing issues etc... It's all there out of the box.
Pro Integrates fully with LDAP
The Lightweight Directory Access Protocol is an application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network.
GitLab EE adds additional functionality over CE such as support for multiple LDAP servers and group sync.
Pro Supports Approvers/Reviewers of Pull/Merge requests
Since 7.12 you can define a minimum number of approvers for merge requests.
Pro "Snippets" support
Snippets are similar to (well-known) GitHub "gists". They are a way to share code or have conversations about anything without needing a full git repo. The implementation here reminds more of a sort of pastebin.
A single instance can handle up to 40,000 users (requires a server with 64 core CPU and 64 GB of RAM) and it can run on multiple application servers to grow beyond that.
Pro Manages large files and binaries with integrated Git Annex
Git Annex enables Git to manage large files (esp binaries) without checking them into Git.
Pro Integrates with other systems by webhooks
Integrates out of the box with services like Bugzilla, Pushbullet, Microsoft Team Notification and many more - one can also add own webhooks to integrate with own services.
Pro Most GitLab EE features become part of GitLab CE after time
EE is the commercial Enterprise Edition, CE is the free and OpenScource Community Edition. Features such as Cycle Analytics were first a part of the EE and are now also available in CE.
Pro Can provide a Docker registry
The default docker.io registry is the docker hub but you can also login to other docker registries. And GitLab provides one for all Repos that make use of this feature.
Pro Integration with third party applications
GitLab integrates with multiple third-party services to allow external issue trackers and external authentication.
GitLab can integrate with many third-party apps to allow external issue tracking and authentication. It can also be integrated with several services, such as:
- Pivotal Tracker
Pro Very feature rich RESTful-API
GitLab exposes a REST API that allows automation possible, like PR bots.
Pro Allows Timetracking with Cycle-Analytics
Very useful project management feature that allows you to know how long it takes to go from the idea to production.
Pro Free and open source
Phabricator is completely free and open source. It's source code is hosted on GitHub.
Pro Actively updated
Phabricator is quickly improving, with bug fixes and new features added often. There is an update to the changelog every couple of weeks.
Pro Bug tracker is included
Includes a bug tracker out of the box. Allows for managing bugs, creating issues, commenting on them and closing them.
Pro Built-in Q&A platform - Ponder
Instead of having to have separate Q&A tool, there's Ponder which takes out the hassle.
Pro Built-in Wiki and pages support
Pro Fully customizeable workboard
You can configure your workspace to deal with tasks, bugs, todo's, etc.
Pro Supports the three major version control systems
Support for Git, SVN and Mercurial is available.
Pro Super flexible bussiness rules (Herald)
Pro Able to review graphical asset changes as well as code.
Pro Fine grained access control
With using Spaces and Project and custom policies you can have any combination of access to any object inside of your own Phabricator instance.
Pro Designed by software engineers for software engineers
The engineering workflow is far superior to Github style branching and merging. Phabricator separates local representations of the repository from remote, which enables a variety of workflow optimisations, like stacked diffs on a single branch.
Pro Code ownership
Users can subscribe to files or even repositories and notifications will be sent when code you are subscribed to is changed.
Pro Command line access (via ARC)
Pro Able to track design mockups
You can track not only code bud also design mockups.
Pro Built-in voting
You can create voting in an instant and need not to rely on external tools.
Pro Built-in blogging platform
There's a great platform which you can use to post stuff, or use as an internal blog, dev blog, release anouncement place and many others.
Pro Built-in chatrooms
Pro Able to manage legal agreements for open source projects
Con Not lightweight
GitLab is demanding, Gitea is a much more lightweight solution which uses less CPU and memory.
Con Not all features are free
GitLab's Service Desk features and some more are only available in GitLab EE.
Con Kind of slow
Con The upgrade process fails more often than not
Even for minor versions such as 9.2.0 to 9.3.0. Sometimes the upgrade failure is silent and only seen when logging in first time after update and an http 502 error is given.
Con Requires at least 1GB of RAM
The default installation is meant for already many users and recommends 2GB of RAM. 1GB is possible but results in some HTTP 500 errors. On a Raspberry Pi 2 it runs fine most of the time, though it eats 75% of the RAM.
Another option is to reduce
unicorn['worker_processes'] in gitlab.rb.
Con Bad code review possibilities
No precommit reviews.
Con Security risks
Con For someone who likes formality, this is not for you
Has slang, sarcasm, and other informal things. If you need to stay formal you shouldn't use this. Personally I like it but others may have different opinion.
Con Difficult to configure
Compared to a solution like Bitbucket Server (granted Phabricator offers more options), it is difficult to configure. Settings are scattered everywhere and you must drill down through several screens to find some of them. Documentation is very complete but also not always in parity with the application itself.