From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 92414 invoked by alias); 21 Oct 2019 01:49:56 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 92114 invoked by uid 89); 21 Oct 2019 01:49:53 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=H*r:sk:server-, video, UD:youtube.com, UD:www.youtube.com X-HELO: simark.ca Received: from simark.ca (HELO simark.ca) (158.69.221.121) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 21 Oct 2019 01:49:51 +0000 Received: from [10.0.0.11] (unknown [192.222.164.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id C26041E598; Sun, 20 Oct 2019 21:49:48 -0400 (EDT) Subject: Re: some thoughts on gerrit To: Andrew Pinski , Tom Tromey Cc: GDB Patches References: <877e4z8ovc.fsf@tromey.com> From: Simon Marchi Message-ID: <6957b59a-b0f0-0bd2-82cb-b249f98ec346@simark.ca> Date: Mon, 21 Oct 2019 01:49:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-10/txt/msg00707.txt.bz2 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