Re: [gentoo-user] automated code validation

2014-12-04 Thread Alec Ten Harmsel
On 12/04/2014 04:08 PM, Rich Freeman wrote: > On Thu, Dec 4, 2014 at 2:36 PM, Alec Ten Harmsel > wrote: >> It'd be cool if Gentoo had some sort of automated workflow (with >> Jenkins, buildbot, whatever) like this: >> >> 1. Receive pull request >> 2. Detect changed ebuild >> 3. test ebuild with e

Re: [gentoo-user] automated code validation

2014-12-04 Thread Rich Freeman
On Thu, Dec 4, 2014 at 2:36 PM, Alec Ten Harmsel wrote: > > It'd be cool if Gentoo had some sort of automated workflow (with > Jenkins, buildbot, whatever) like this: > > 1. Receive pull request > 2. Detect changed ebuild > 3. test ebuild with etest > > This will take a lot of work to set up, and

Re: [gentoo-user] automated code validation

2014-12-04 Thread Alec Ten Harmsel
On 12/04/2014 02:02 PM, Alex Brandt wrote: > Hey James, > > I've removed the original content for length but I love the > ideas you've put together for an overarching testing strategy. > > I've begun work on a small ebuild testing framework, etest [1], > that I believe fits into your model quite

Re: [gentoo-user] automated code validation

2014-12-04 Thread Alex Brandt
Hey James, I've removed the original content for length but I love the ideas you've put together for an overarching testing strategy. I've begun work on a small ebuild testing framework, etest [1], that I believe fits into your model quite well. It uses docker images for isolation and repeata