General discussion about Chef

[chef] Re: Re: Continuous Integration


Chronological Thread 
  • From: Chad Woolley < >
  • To:
  • Subject: [chef] Re: Re: Continuous Integration
  • Date: Wed, 7 Jul 2010 18:24:07 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=OSE6BFm/vfKL8k9WWpP3kTbuRGq6Ca5uyyoZJ4fdRq3l2nGdTP10Ir6d8kPsDJejPm fN3uC3MOHgRiR+L0MfmUTj96NLz7ytHPoQuPT3TssD9uWrA+hXPkW7MbqHep8Bpq6DEy C/rb4Il7IaqnS6rvyvmsM7QOHZ6kXJqsX5Pjs=
On Wed, Jul 7, 2010 at 5:27 PM, AJ Christensen 
< >
 wrote:
> This hasn't been invented yet. Look forward to it :-)
>
> On 8 Jul 2010 12:26, "Andrew Shafer" 
> < >
>  wrote:
>> How are people testing their cookbooks?
>>
>> Who has continuous integration set up?
>>
>> Anyone favor particular approaches, insightful recommendations or
>> scaffolding to share before I set off to reinvent a square wheel?

I've got some ideas.  You can use SSH to perform remote assertions
(e.g. zero or nonzero return code) on the converged box.  E.g. - check
that a package is installed, a service is running, etc.  These tests
could be written in any test framework/language which allows you to
invoke SSH and check the return code (or parse SSH command output).

Thoughts?  Anyone done anything along these lines?

-- Chad

Archive powered by MHonArc 2.6.16.

§