From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Automatically building packages affected by submitted patches Date: Mon, 04 Mar 2019 11:27:48 +0100 Message-ID: <87ef7nvsrf.fsf@elephly.net> References: <87tvgmfgkw.fsf@cbaines.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:54908) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h0kpK-00041m-Gg for guix-devel@gnu.org; Mon, 04 Mar 2019 05:28:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h0kpJ-0001j6-Jj for guix-devel@gnu.org; Mon, 04 Mar 2019 05:28:06 -0500 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21045) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h0kpJ-0001bn-5z for guix-devel@gnu.org; Mon, 04 Mar 2019 05:28:05 -0500 In-reply-to: <87tvgmfgkw.fsf@cbaines.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Christopher Baines Cc: guix-devel@gnu.org Hey Chris, > In short, following on from some previous emails about Patchwork [1] and > tracking and inspecting how Guix changes over time [2], I've got to the > point where I have a very rough setup for building packages changed by > patches sent to the guix-patches mailing list. This is great! > With the goal of displaying a check in Patchwork about the > build status of the affected packages, I need to compare what's been > build by my Cuirass instance, with what https://ci.guix.info/ has > built. To do this, my current plan is to have the Guix Data Service > monitor a number of Cuirass instances somehow, extract information from > them and store it. Would it not make sense to have the build farm perform the builds instead of having a separate Cuirass instance? > - Looks at patch series in the Patchwork database that have been > processed through the patchwork-test-series job in Laminar. Is the Laminar job something that could become part of Cuirass itself? -- Ricardo