From owner-freebsd-testing@FreeBSD.ORG  Tue Feb 24 20:04:18 2015
Return-Path: <owner-freebsd-testing@FreeBSD.ORG>
Delivered-To: freebsd-testing@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D2684F73;
 Tue, 24 Feb 2015 20:04:18 +0000 (UTC)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com
 [IPv6:2a00:1450:4010:c04::22f])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 53227ED0;
 Tue, 24 Feb 2015 20:04:18 +0000 (UTC)
Received: by lbvn10 with SMTP id n10so27465291lbv.6;
 Tue, 24 Feb 2015 12:04:16 -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:cc:content-type;
 bh=XdDEVLkyixP+7WbpskNbP61uffrhtk0Jz9QgYSdzoOA=;
 b=E45hBWa3vc9a5kJYOG0jfyv7XQz4RoqG8PTy8iJ/wGPdTx/kEHKBVt0ZQBamu6cugb
 EJDm4NMjFLhL/SVbgVdvndvNHaLdjZ2yVJ0S51T+WNyBJBkA21s2C/89CdeL8yQLyKGA
 rXXmCRQa5E3Hrsacv3gnK6yCGUgjuPu3Dus464VQbdl3dwXSudr6YK2iD2xGWJbiGivc
 9EKKH5Rz2GzKJ5Rd/XYOxYpipu2T1AjHXV7fV8g9ZECy98oLed/gzS5fQmTm8DwWU+OV
 2Vf537Ge7gO33TYRGsthA4j+aHpiiFsJSHhj59kULN48+PpuIfJEJb0gbSeVsaGD3844
 a5oA==
MIME-Version: 1.0
X-Received: by 10.112.139.168 with SMTP id qz8mr15751332lbb.84.1424808256091; 
 Tue, 24 Feb 2015 12:04:16 -0800 (PST)
Sender: crodr001@gmail.com
Received: by 10.112.82.164 with HTTP; Tue, 24 Feb 2015 12:04:15 -0800 (PST)
In-Reply-To: <54EC1310.30509@freebsd.org>
References: <CAPyFy2DKMktGV2yp=u2aesoiGH=s_VMksO_7HkPwmwi6MU3S4Q@mail.gmail.com>
 <CAG=rPVfvjVor-rt1S1TprOKcfvQL93m8zC4UNq+pdqDRcfxqjA@mail.gmail.com>
 <54EBF759.1060002@freebsd.org> <54EC1310.30509@freebsd.org>
Date: Tue, 24 Feb 2015 12:04:15 -0800
X-Google-Sender-Auth: URD1IMB2sDmkogcgd19VKeFAYuk
Message-ID: <CAG=rPVe4c+=dFr7M3rNai_yxqS=HSvpu-qKqbKtH9gttqGawhw@mail.gmail.com>
Subject: Re: Running tests as a developer prior to commit
From: Craig Rodrigues <rodrigc@FreeBSD.org>
To: Alfred Perlstein <alfred@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>
X-BeenThere: freebsd-testing@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Testing on FreeBSD <freebsd-testing.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-testing/>
List-Post: <mailto:freebsd-testing@freebsd.org>
List-Help: <mailto:freebsd-testing-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2015 20:04:19 -0000

On Mon, Feb 23, 2015 at 9:58 PM, Alfred Perlstein <alfred@freebsd.org>
wrote:

>
>
> On 2/23/15 11:00 PM, Allan Jude wrote:
>
>
>>>
>> Doesn't phabricator have some hooks to launch tests of a "proposed"
>> patch? This could help catch the errors before they are committed
>>
>>
> Yes we should hook that.
>
>
There is a blog post which describes this type of workflow with Phabricator:
http://www.dctrwatson.com/2013/01/jenkins-and-phabricator/

It's not like we need a magician or warlock to put this together, but somone
has to write the code to do the integration.

--
Craig