This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: some thoughts on gerrit
- From: Simon Marchi <simark at simark dot ca>
- To: Andrew Pinski <pinskia at gmail dot com>, Tom Tromey <tom at tromey dot com>
- Cc: GDB Patches <gdb-patches at sourceware dot org>
- Date: Sun, 20 Oct 2019 21:49:48 -0400
- Subject: Re: some thoughts on gerrit
- References: <877e4z8ovc.fsf@tromey.com> <CA+=Sn1kES73xVmzismyyf3XADKGm98+X6_QoZ5BmhOUnkWqYUQ@mail.gmail.com>
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