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

[Noah Kantrowitz < >]

For long secrets you can also put them in a private S3 (or similar bucket) 
and just put the access key in your env vars, and then download the file at 
run time. (ex 
https://github.com/balanced-cookbooks/balanced-berkshelf-api/blob/master/.travis.yml#L10)

--Noah

On Apr 2, 2014, at 9:20 PM, "Julian C. Dunn" 
<
 >
 wrote:

> 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       ]

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail