From owner-freebsd-testing@FreeBSD.ORG  Tue Feb 24 21:16:51 2015
Return-Path: <owner-freebsd-testing@FreeBSD.ORG>
Delivered-To: freebsd-testing@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 2481FBC4;
 Tue, 24 Feb 2015 21:16:51 +0000 (UTC)
Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196])
 by mx1.freebsd.org (Postfix) with ESMTP id 03A8A973;
 Tue, 24 Feb 2015 21:16:51 +0000 (UTC)
Received: from AlfredMacbookAir.local (unknown [12.133.26.10])
 by elvis.mu.org (Postfix) with ESMTPSA id 7685F341F910;
 Tue, 24 Feb 2015 13:16:50 -0800 (PST)
Message-ID: <54ECEB17.2040804@freebsd.org>
Date: Tue, 24 Feb 2015 16:20:23 -0500
From: Alfred Perlstein <alfred@freebsd.org>
Organization: FreeBSD
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Craig Rodrigues <rodrigc@FreeBSD.org>
Subject: Re: Running tests as a developer prior to commit
References: <CAPyFy2DKMktGV2yp=u2aesoiGH=s_VMksO_7HkPwmwi6MU3S4Q@mail.gmail.com>	<CAG=rPVfvjVor-rt1S1TprOKcfvQL93m8zC4UNq+pdqDRcfxqjA@mail.gmail.com>	<54EBF759.1060002@freebsd.org>	<54EC1310.30509@freebsd.org>
 <CAG=rPVe4c+=dFr7M3rNai_yxqS=HSvpu-qKqbKtH9gttqGawhw@mail.gmail.com>
In-Reply-To: <CAG=rPVe4c+=dFr7M3rNai_yxqS=HSvpu-qKqbKtH9gttqGawhw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
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 21:16:51 -0000


On 2/24/15 3:04 PM, Craig Rodrigues wrote:
>
>
> On Mon, Feb 23, 2015 at 9:58 PM, Alfred Perlstein <alfred@freebsd.org 
> <mailto: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.
Last I checked I'm not on cluster admin or anything admin because people 
are afraid I would turn the cluster into a social networking backend for 
a dating website (or ascii generator) so I am really not in a position 
to do anything about this.

By the way, is Phabricator open to the wild yet?  Like is it anywhere 
close to github?  Or is it still closed door?

-Alfred