- From: Ringo De Smet <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: My first chef cookbook
- Date: Tue, 29 Jun 2010 09:45:22 +0200
- 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:content-transfer-encoding; b=r6ZrugovYLNJHkMAKrY5pBp65hFOtBUmH6P3oa2XsVmJYxXl2Sk/IgLNLwTXZdrTFG fSjQzQv/o0mxmPv17TtlV9LdtmlyDPOmlnvXhRNkuPvIgOUhNugJ5571KAleTLKbRrfm CMSJnU/H0qneO4UeAwsspO8un5xEXc4VTKwc0=
Mike,
On 29 June 2010 09:22, Mike Bailey
<
>
wrote:
>
>
I agree that this is a better strategy. I only wish I was always
>
so disciplined. :-)
I am currently in the role of Release Manager, and without this
discipline and Chef, I would be drowning! :-)
Chef is used for the configuration of all the various types of Hudson
(1) build slaves. Setting up additional slaves goes quite fast:
a. existing setup: launch base VDI with Chef client installed,
register and assign the proper role(s)
b. new setup: in a few hours I can have a recipe written or updated
and tested, and then I am back at step a.
Next to that, I am able to offer pre-configured virtual machines to
our developers by using Chef in combination with Vagrant (2).
(1)
http://hudson-ci.org
(2)
http://vagrantup.com
Ringo
Archive powered by MHonArc 2.6.16.