RSS of outstanding changes in a gerrit project

[PO Bengtsson]

Hi all,

First pardon me, if this has been discuss or already exists. I
searched the forum archive but could not find a match. Pointers
appreciated.

For a gerrit project, I would like to get a report on what changes/
patches have been pushed for review, but is not yet committed or
rejected.

This information I would like to use in 2 ways.

The first way is to create an Eclipse plugin that takes the patches
information and annotates the code in Eclipse so that the dev get
hints on what lines of code is pushed for review. Then the dev can
proceed with caution or help in reviewing the patch given the rights
to do so.

The second way is to provide a gauge that shows how much integration/
review burden is waiting in gerrit, to provide teams and managers a
fact based way to act when priorities should shift more towards
review.

I think a solution could be to have something like an RSS flow for a
gerrit project, with the information and then the Eclipse plugin
subscribes to that flow and the gauge tool subscribes to that same
flow.

Eager to hear your thoughts on this.

Best Regards,

PO Bengtsson

[Shawn Pearce]

On Wed, Jul 13, 2011 at 01:59, PO Bengtsson <pero...@gmail.com> wrote:
> First pardon me, if this has been discuss or already exists. I
> searched the forum archive but could not find a match. Pointers
> appreciated.
>
> For a gerrit project, I would like to get a report on what changes/
> patches have been pushed for review, but is not yet committed or
> rejected.

There isn't an RSS feed. You may be able to get some of what you want
from a query, like `ssh -P 29418 server gerrit query status:open`.
There is a "hidden" way to run this query via the web,
http://server/query?q=status:open ... if I can remember the URL
correctly. :-)

> This information I would like to use in 2 ways.
>
> The first way is  to create an Eclipse plugin that takes the patches
> information and annotates the code in Eclipse so that the dev get
> hints on what lines of code is pushed for review. Then the dev can
> proceed with caution or help in reviewing the patch given the rights
> to do so.

You should look at/talk to the Mylyn Reviews team. Mylyn is building a
connector to Gerrit Code Review. The JGit/EGit team is involved in
this effort too.