From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-160405-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id ED64D1389E2
for <garchives@archives.gentoo.org>; Thu, 4 Dec 2014 21:08:21 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 50DF2E0952;
Thu, 4 Dec 2014 21:08:17 +0000 (UTC)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 43B8BE0884
for <gentoo-user@lists.gentoo.org>; Thu, 4 Dec 2014 21:08:16 +0000 (UTC)
Received: by mail-ie0-f172.google.com with SMTP id tr6so16624427ieb.31
for <gentoo-user@lists.gentoo.org>; Thu, 04 Dec 2014 13:08:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:date:message-id:subject
:from:to:content-type;
bh=JdE5QuRn1sPMPSOuaI2Pwi2qONyblSDLtWPtYbL34p0=;
b=x84P3+VSbi41tKwDH6VL8TEEcPh2yxtRX/FVNKuo7OzF3ctR7cWdinJjvy7U5bsjnR
xKf3Y9jVcGnEBqfObdiaiZUZym+83pMWqXHJls8IFItOdsdCsotKFByNo36/AvzDkof2
ZTwo7uMlNmDiZ/nntDws9fFjWFB8xt+KlJnZHPCudJDGDKv56CYLgb1g9OvQk/zwmBSp
rBljLAWbGwYlWF88RITXFOsbpDYLKv4GsXXLbt0U4bR/d1UKOq7SDXmXPsETDQP0GjzO
qSjgINzvneCcw888mVeO1+1HUCSz3g5tZOEgu9b5GAz2MXWDCagcwp/UV55hFhmst7e+
jceQ==
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.107.12.234 with SMTP id 103mr11875290iom.71.1417727295513;
Thu, 04 Dec 2014 13:08:15 -0800 (PST)
Sender: freemanrich@gmail.com
Received: by 10.107.9.80 with HTTP; Thu, 4 Dec 2014 13:08:15 -0800 (PST)
In-Reply-To: <5480B7A8.5030204@alectenharmsel.com>
References: <loom.20141201T175046-420@post.gmane.org>
<3306609.71mJRjCGqA@elijah>
<5480B7A8.5030204@alectenharmsel.com>
Date: Thu, 4 Dec 2014 16:08:15 -0500
X-Google-Sender-Auth: 3IaB90EcJv6r-uWeqvBaReuP1PY
Message-ID: <CAGfcS_=FjsWFjPEtuoAt_LBJyNskJaV3ozVbVb1sa_8-hDJzJQ@mail.gmail.com>
Subject: Re: [gentoo-user] automated code validation
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
X-Archives-Salt: e1e42c3f-4cbf-41cb-a145-366b8cd713a5
X-Archives-Hash: eda249e0fc46f60eb076b5b5b8bcb7d3
On Thu, Dec 4, 2014 at 2:36 PM, Alec Ten Harmsel
<alec@alectenharmsel.com> wrote:
>
> It'd be cool if Gentoo had some sort of automated workflow (with
> Jenkins, buildbot, whatever) like this:
>
> 1. Receive pull request
> 2. Detect changed ebuild
> 3. test ebuild with etest
>
> This will take a lot of work to set up, and depending on how my workload
> is next semester, I would love to help out as much as possible.
>
I've wondered the same thing, and maybe after sufficient bikeshedding
something like this would be a good GSoC project as well. Running
repoman is another possibility.
One trick is that a pull request could impact multiple packages
(eclass changes, dependency updates, etc). In these cases running
repoman probably adds more value than full tests. Either way there
will potentially be a high cost to do the testing, which could create
a backlog if we queue things up (not queuing things creates other
problems). Repoman false-alarms is another potential issue with this.
So, it may not be a trivial thing to do, but some kind of CI workflow
would be a wonderful thing to have.
--
Rich