- From: "Julian C. Dunn" <
>
- To: "
" <
>
- Subject: [chef] Re: Re: Automated test-kitchen runs?
- Date: Thu, 3 Apr 2014 00:20:42 -0400
Yep, I started replicating what Sean O'meara is doing, and I have some
notes here for having Travis drive T-K to do testing on DigitalOcean:
https://github.com/juliandunn/sauceconnect/blob/master/TRAVIS.md
Total rough draft, but it does work. Blog post will follow at some point.
- Julian
On Thu, Mar 27, 2014 at 7:19 PM, Noah Kantrowitz
<
>
wrote:
>
Run test-kitchen from travis? Super easy with kitchen-rackspace and
>
somewhat easy with kitchen-ec2.
>
>
--Noah
>
>
On Mar 27, 2014, at 4:18 PM, Christopher Armstrong
>
<
>
>
wrote:
>
>
> Ohai Chefs,
>
>
>
> We have rubocop and foodcritic configured to run on Travis CI to
>
> automatically check our pull requests, which is awesome. I verify each
>
> build with test-kitchen before I cut a new cookbook release, but this is
>
> getting very time consuming to run manually each time. For the java
>
> cookbook, testing different java versions on various platforms results in
>
> a ton of individual runs. I'd love to set up a system to automatically run
>
> test-kitchen and then give me the red/green light.
>
>
>
> Has anyone tried doing this and could recommend some tools/workflows?
>
>
>
> Thanks,
>
>
>
> Chris
>
>
>
>
>
--
[ Julian C. Dunn
<
>
* Sorry, I'm ]
[ WWW:
http://www.aquezada.com/staff/julian * only Web 1.0 ]
[
gopher://sdf.org/1/users/keymaker/ * compliant! ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]
Archive powered by MHonArc 2.6.16.