Date: Thu, 12 Mar 2015 21:12:52 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Craig Rodrigues <rodrigc@FreeBSD.org> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org> Subject: Re: Phabricator and automatic build testing Message-ID: <5501F344.1030105@selasky.org> In-Reply-To: <CAG=rPVcWbdA==xYcqnBTBjDv-bPfvSNfEg3Bv6O=0=qsAYczKg@mail.gmail.com> References: <5501EED7.4060801@selasky.org> <CAG=rPVcWbdA==xYcqnBTBjDv-bPfvSNfEg3Bv6O=0=qsAYczKg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/12/15 20:59, Craig Rodrigues wrote: > On Thu, Mar 12, 2015 at 12:53 PM, Hans Petter Selasky <hps@selasky.org> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5501F344.1030105>