Thursday, November 10, 2016

5 reasons to use EGerrit - #1 – Comment directly from the language editor

To celebrate the release of EGerrit 1.1, we are enumerating the top 5 features of the tool.

#1 - Comment directly from the language editor

When you are performing the review of a large change, the compare editor may no longer be satisfactory because you want to have multiple files opened, or because you want to see more information about the source code. Yet, you still want to be able to enter and see comments while you are in the regular editor (e.g. Java editor).

This is exactly what the EGerrit’s integration with the Eclipse markers let you do. When you checkout a review, a marker will be associated with each comment from the checked-out revision; and each file that is part of the review will feature a context menu to let you enter a new comment (see picture). Each marker created will be shown in the “Markers view” and will have associated quick-fixes letting you reply to the comment, or delete it if it is a draft.

This concludes our top 5 of EGerrit features, and we hope that you will take the time to try out the tool and provide us with feedback, and feature requests. Of course 1.1 is not the end, and we are steadily improving the tool by making the workflows smoother, and deepening the integrations. Our current release plan is to ship a new version of EGerrit with Neon.2 in December 2016, with Neon.3 in February 2017, and with Oxygen in June 2017. If you can’t wait for those, you can always get our latest I build from one of our repository.

Top 5 EGerrit features:

Thursday, November 03, 2016

5 reasons to use EGerrit - #2, Compare against workspace

To celebrate the release of EGerrit 1.1, we are enumerating the top 5 features of the tool.

Reason #2, Compare against workspace.

When you’ve authored a review and are receiving feedback, your next duty is to take this feedback into account. In order to make that as simple as possible, the compare editor offers the ability to show on one side the patchset that contains the comments, and on the other the files from the workspace in which you can directly code your changes (see picture).
Taking comments into accounts
Taking comments into account.

How to make that work?

  • Download the review (so the most recent revision is now in your workspace);
  • open the compare editor;
  • and set the revision with comments on the left side of the compare editor and the workspace on the right side.
Now, as you are going through the comments, you can directly take them into account without even going back to a full blown editor. Pretty slick isn’t it?

Comparing a patchset to the files in the workspace has additional benefits:
  • Gauge the impact of an incoming review on your on-going work. Let’s say that while you are working on a new feature, someone publishes a new review touching some of the files you are modifying. Using the compare with workspace feature, you can quickly see if and how the changes in the new review overlaps with your on-going work;
  • Measure the impact of an additional change you would like to do on the current review. Let’s imagine that you would like to perform additional changes in the code under review, then you could simply start editing the code and then see how much extra changes it creates on top of the existing one.

You can download EGerrit from the Neon release repo or from the Eclipse Marketplace. For questions, you can connect with us on; and for bugs or to take a peek at the future you can see our Kanban board.