From owner-freebsd-testing@FreeBSD.ORG Thu Mar 12 20:12:09 2015 Return-Path: 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 49D5AEC2; Thu, 12 Mar 2015 20:12:09 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0ADE3353; Thu, 12 Mar 2015 20:12:09 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 45C0C1FE023; Thu, 12 Mar 2015 21:12:07 +0100 (CET) Message-ID: <5501F344.1030105@selasky.org> Date: Thu, 12 Mar 2015 21:12:52 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Craig Rodrigues Subject: Re: Phabricator and automatic build testing References: <5501EED7.4060801@selasky.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 20:12:09 -0000 On 03/12/15 20:59, Craig Rodrigues wrote: > On Thu, Mar 12, 2015 at 12:53 PM, Hans Petter Selasky > wrote: > >> Hi, >> >> Is it possible to integrate Phabricator (reviews.freebsd.org) with >> automatic build testing? >> >> Keep me CC'ed, hence I'm not subscribed to this list. >> > > > Can you describe a workflow that you would like to see with > reviews.freebsd.org and automatic build testing? Hi, Sometimes it would be nice if you could check a box and say: 1) Apply the patch to 8-stable or 9-stable or 10-stable or head 2) Build universe (or all kernel or all userspace programs) Sometimes doing the universe kills a lot of time, and I frequently end up simply going into the kernel modules or programs that are affected by a change and only build those to save time. Maybe phabricator could have something similar, that you can select a set of directories and subdirectories or kernel modules to build after applying a change? Maybe also with different CFLAGS, like debug/no debug. > > It is quite possible to integrate phabricator with a continuous integration > system like Jenkins, for example. > Here is a blog post on giving one example of how it can be done: > > http://www.dctrwatson.com/2013/01/jenkins-and-phabricator/ > > If the FreeBSD project was more tightly integrated with git and github, > there would be a lot > of scripts that we could instantly leverage to do this kind of thing. > There are many projects > that I contribute to on github, where if you do a github pull request, > automated scripts > build and test the change in the pull request, and report the results. FreeBSD does have a github mirror. Can't that be used with Phabricator, if some plugins require GIT? > In FreeBSD, we are not there yet, so we need to write the scripts to > integrate with the stuff > that we have, i.e. bugzilla, phabricator, jenkins, etc. > > The other piece of the puzzle is that someone needs to step up and do the > work to make > this happen with phabricator and jenkins (or whatever scripts we want to > use). > > I've done a lot with jenkins and kyua in the past year, but I could > definitely use more help > from people interested in working on this stuff, and taking it to the next > level. I appreciate your work with Jenkins. --HPS