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
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 well.
On Thu, Dec 4, 2014 at 2:36 PM, Alec Ten Harmsel
a...@alectenharmsel.com 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
On 12/04/2014 04:08 PM, Rich Freeman wrote:
On Thu, Dec 4, 2014 at 2:36 PM, Alec Ten Harmsel
a...@alectenharmsel.com 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
Howdy!
Software validation has a long, often divisive history, we should all
be aware of. I've seen several Computer Scientists (PH.Dumasses) go to
fists over validation. It seems surreal now, but, it was hilarious
at the time as none of the (3) involved in the fists_to_cuff had a clue
about
5 matches
Mail list logo