Date: Tue, 24 Feb 2015 12:04:15 -0800 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: Alfred Perlstein <alfred@freebsd.org> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org> Subject: Re: Running tests as a developer prior to commit Message-ID: <CAG=rPVe4c%2B=dFr7M3rNai_yxqS=HSvpu-qKqbKtH9gttqGawhw@mail.gmail.com> In-Reply-To: <54EC1310.30509@freebsd.org> References: <CAPyFy2DKMktGV2yp=u2aesoiGH=s_VMksO_7HkPwmwi6MU3S4Q@mail.gmail.com> <CAG=rPVfvjVor-rt1S1TprOKcfvQL93m8zC4UNq%2BpdqDRcfxqjA@mail.gmail.com> <54EBF759.1060002@freebsd.org> <54EC1310.30509@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVe4c%2B=dFr7M3rNai_yxqS=HSvpu-qKqbKtH9gttqGawhw>