Gerrit has a robust code review workflow. It makes it easy to manage changes and ensures that only reviewed code gets merged. We can track revisions and leave detailed comments directly on the code. There is strong integration with Git and Jenkins. It also has a clean UI. Additionally, we can manage user-level access to control who has the ability to merge code. Review collected by and hosted on G2.com.

The integrations with some modern tools feel limited compared to other code review platforms. There’s also a steep learning curve for new team members, which can slow onboarding. On top of that, the initial setup and configuration can be time-consuming and technically challenging, especially if you’re trying to get everything aligned from the start. Review collected by and hosted on G2.com.

Patchset comparision

Options to cherry-pick to multiple branches & take patchsets

Multi comments option for each line in the code file

Mark & Edit code to resolve comments

Easy to find the changes using user or file name

Add topic option to merge all the dependency changes together Review collected by and hosted on G2.com.

Difficult to resolve merge conflict directly from gerrit.

Most often will sign out automatically and keep ask user to sign-in.

Downloaded patches will be in invalid format always and sometimes patch will not apply properly Review collected by and hosted on G2.com.

Gerrit is a robust tool for facilitating code reviews and managing Git repositories. Its inline commenting and change set features allow for precise feedback and easy tracking of modifications. Integration with CI tools like Jenkins automates testing and deployment processes, ensuring high code quality and efficient workflows.

Ease of Use: While Gerrit offers powerful features, it has a steep learning curve.

The interface can be challenging for beginners, requiring time and effort to master.

Ease of Implementation: Implementing Gerrit can be complex, especially for large-scale projects.

Proper planning and understanding of its architecture are crucial for a smooth setup.

Customer Support: Gerrit benefits from a strong community and various support resources, including forums, mailing lists, and chat rooms. However, direct customer support is limited compared to commercial tools.

Frequency of Use: Gerrit is frequently used for code review and repository management tasks, making it a core tool in many development workflows.

Number of Features: Gerrit is feature-rich, offering tools for code review, repository management, and integration with CI/CD pipelines. This makes it highly customizable and versatile.

Ease of Integration: Gerrit integrates seamlessly with numerous tools and platforms, including CI tools like Jenkins, enhancing its functionality and flexibility. Review collected by and hosted on G2.com.

Gerrit can be challenging to set up and configure, especially for new users.

The user interface, while functional, can feel outdated and less intuitive compared to other modern code review tools. Additionally, managing permissions and integrating with other tools can sometimes be complex Review collected by and hosted on G2.com.

Excellent features to support code review for different technologies and easy integration with latest SCM and CI tools like git, Jenkins, TeamCity, bamboo, GitHub and GitLab Review collected by and hosted on G2.com.

Better documentation and community support for issues. Also, better integration with TFS and Azure DevOps would make it more usable for .net community developers as well. Review collected by and hosted on G2.com.

The best feature has to be the Code review. The code review gives a side-by-side comparison of the changes made and highlights additions or deletions of code made, also it has gradings ranging from -2 to +2, with -2 being the worst and +2 the best. Review collected by and hosted on G2.com.

Commits are made in Hierarchical order, if a parent commit isn't merged one cannot merge its child commit even though both the commits deal with totally different files. Review collected by and hosted on G2.com.

Remote file systems are likely perform than local ones Review collected by and hosted on G2.com.

One commit per file or per instance of the same fix, i did not like to say that in glustered Review collected by and hosted on G2.com.

I am using Gerrit since last 4 years and my experience has been great with this tool because of the following reason:- 1. Maintains entire code review history effectively. 2. Reviewer and the developers can respond and communicate easily. 3. Easy to integrate with Jenkins and Jira. Review collected by and hosted on G2.com.

I don't have anything to dislike about this tool as I had fantastic experience with it. Review collected by and hosted on G2.com.

I would feel very good to work with Gerrit, as it was the best way to send the code reviews and patch sets and replying to the comments are very useful Review collected by and hosted on G2.com.

I don't feel anything till now, I will post if got anything needs to change Review collected by and hosted on G2.com.

The best thing is it's a distributed collaborating tool that can help in managing good quality code. You can add some test cases, you can fix compilation errors and you can manage version history for future reference. Review collected by and hosted on G2.com.

It can work only with GIT and it is slower than other available collaborating tools. Review collected by and hosted on G2.com.

Simple interface

Easy to adapt and usability Review collected by and hosted on G2.com.

I dont think I disliked anything as of now Review collected by and hosted on G2.com.