- From: Chad Woolley <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration
- Date: Fri, 9 Jul 2010 12:26:30 -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:content-transfer-encoding; b=pdXPl9JwX+WEIxoglPeHDQN9g9Mn73lsVQ4nOw04mWrmYGcRf017HTeHX+thWTl+iA kqCBPkHT71IkNk38BnnbJy6mhMsVU2LE+LFglVGzb1cQw94GXk90aN4fpQLczWX7Q08R bavuTUPIgPo8GPcTtDK2wK5aYj1O2mtlqvZfY=
On Fri, Jul 9, 2010 at 12:20 PM, Jeremy Deininger
<
>
wrote:
>
Hey guys,
>
Thought I'd chime in with my experience testing system configuration code @
>
RightScale so far. What we've been building are integration style cucumber
>
tests to run a cookbook through it's paces on all platforms and OSs that we
>
support.
>
>
First we use our API to spin up 'fresh' server clusters in EC2, one for
>
every platform/OS (variation) that the cookbook will be supporting. The
>
same could be done using other cloud APIs (anyone else doing this with
>
VMware or etc?) Starting from scratch is important because of chef's
>
idempotent nature.
>
>
Then a cucumber test is run against every variation in parallel. The
>
cucumber test runs a series of recipes on the cluster then uses what we call
>
'spot checks' to ensure the cluster is configured and functional. The spot
>
checks are updated when we find a bug, to cover the bug. An example spot
>
check would be, sshing to every server and checking the mysql.err file for
>
bad strings.
>
>
These high level integration tests are long running but have been very
>
useful flushing out bugs.
>
-J
This sounds like exactly the right approach. Is it open source (yet)?
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, (continued)
[chef] Re: Re: Re: Re: Re: Re: Continuous Integration, Daniel Pittman, 07/08/2010
- [chef] Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Thom May, 07/08/2010
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Joel Merrick, 07/08/2010
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Daniel Pittman, 07/09/2010
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Andrew Shafer, 07/09/2010
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Michael Hale, 07/09/2010
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Jeremy Deininger, 07/09/2010
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Chad Woolley, 07/09/2010
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Trotter Cashion, 07/09/2010
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Jeremy Deininger, 07/09/2010
[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Ryan Creasey, 07/09/2010
[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Jesse Nelson, 07/10/2010
[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Chad Woolley, 07/10/2010
[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Jon Wood, 07/14/2010
[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Continuous Integration, Chad Woolley, 07/09/2010
Archive powered by MHonArc 2.6.16.