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

[Daniel Pittman < >]

Thom May 
<
 >
 writes:

> We had some good conversations in this area at Velocity. What we came down
> to is that possibly the path of least resistance approach is to leverage the
> fact that chef recipes are (mostly) idempotent, so that Chef itself knows if
> a cookbook has actually worked successfully.

[...]

> BDD - as was pointed out again at LdnDevOps last week - for cookbooks could
> end up being just restating your cookbook in a different language

*nod*  I will confess, if I was going to look at this in production I would be
aiming for a set of network-wide "does it work" tests ... and have a view to
hooking them to my monitoring system to run routinely, not just when the CMS
made a change.

I don't see substantial value in anything much beyond watching the outcome
of a run after changes, to make sure it did what was expected, good
monitoring, to catch what isn't expected, and good syntax checks.

        Daniel
-- 
✣ Daniel Pittman            ✉ 

 
            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons