Re: some thoughts on gerrit

[Simon Marchi <simark@simark.ca>]

On 2019-10-20 7:16 p.m., Andrew Pinski wrote:
> Hi,
>  First, we use gerrit internally at Marvell.  I have another benefit
> for gerrit, which is not listed here.  You can configure gerrit to
> hook into an automation service which will give then automated
> feedback.  E.g. we use it to run check patch (on Linux kernel patches
> and others) and then if the patch builds and tests it on a few
> platforms.
> I don't know if you could use patchworks to do that though.
> 
> Thanks,
> Andrew Pinski

Hi Andrew,

Indeed, this is part of what we want to do, make it really easy to test
a given patch on the buildbot.

Git-based patch systems like Gerrit make it really easy to do that.  Because
people push git commits, it's always works to just check out those commits to
test them.

With email patches, we can try to apply patches, but they may not apply cleanly,
either because the person didn't use git-send-email, or the patches were based
on an older commit.

It seems like patchwork, has an event API that can tell you when a new patch
is detected, and that can be used to trigger CI builds:

https://patchwork.readthedocs.io/en/latest/usage/overview/#events

The CI system can then attach some metadata as "checks":

https://patchwork.readthedocs.io/en/latest/usage/overview/#checks

Here's a FOSDEM video I found about these features:

https://www.youtube.com/watch?v=zSexR5c4Vxk

Simon