[chef] Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration


Chronological Thread 
  • From: Joel Merrick < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration
  • Date: Thu, 8 Jul 2010 13:58:00 +0100
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=A6INmFNEwVfhDiBtIghlOCPlEo01coDzgBqnHoPVquT2Odp/kyePd/ZDoqV9h9XTVW zXn84+s2B0gMMOD7vOJmCO6dtCd1+4YHzS63CaR4aL70gNtfuxyG50QCI1aFPQHnmc9f O1zGYqFSAXifqdO8B7guaj/Gw+hH+K15lI5Eo=

This is something I have an active interest in too as I'm in the
planning/feasibility stages of such a project.

Initially I was thinking of driving the test with expect scripts to
test the system on the 'first pass' after it's been converged by Chef.
That has now grown to include testing Cucumber and the like.

The plan is to automatically build each particular set of systems in
the production configuration tree in VMs (every night/week) and ensure
that the tests pass, that way we know of any issues pre-deployment

In addition to this we'd like to run the same tests post-deployment
and produce a report to act as a sign off for the customer/client.

If anyone gets any further with this or has real world experience or
wants to collaborate, I'd be most interested!

Joel

-- 
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'



Archive powered by MHonArc 2.6.16.

§