[chef] Re: Re: Automated test-kitchen runs?

[Tony Burns < >]

I just began using the (newish?) paradigm I saw in the Opscode nginx cookbook 
to test my cookbooks for a side project via Travis and Digital Ocean. The 
cookbooks at https://github.com/todonts-cookbooks are linted with rubocop and ;
foodcritic, unit tested with chefspec, and and integration tested on DO via 
the kitchen-digitalocean provider and serverspec (I don't think I've 
committed any of the serverspec tests yet). One nice thing you can do with 
Travis is use the build matrix to run your test-kitchen suites in parallel 
during the build. The most complete example I have up right now is the nginx 
cookbook for my project (https://github.com/todonts-cookbooks/todonts-nginx), 
but you can see the build-matrix stuff in action on the todonts-app cookbook 
(https://github.com/todonts-cookbooks/todonts-app). Props to the folks at 
Opscode for writing all the original harnessing.

Regards,
Tony

--
Tony Burns
Operations Engineer / Software Developer
Quad Learning, Inc.
1150 17th St Ste 310, Washington, DC 20036
c. 608.799.2000 p. 202.525.1078 f. 202.652.1075

On Mar 27, 2014, at 19:19, 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
>> 
>> 
>