* hai wu [2011-03-20]:
> I am interested in the details using cucumber-puppet to verify catalog
> compilation. Could you please elaborate on it?
I setup a catalog policy that applies to all catalogs, by specifying a
scenario for each of our servers like so:
@node
Given a node specified by "$nodefact"
When I compile its catalog
Then compilation should succeed
And all resource dependencies should resolve
And all files should require their owner
And all services should have a nagios check
And all websites should have a nagios check
...
As the scenarios are almost identical, I generate the policy from a
script. When someone pushes a change, our CI server runs the complete
test suite to verify all server catalogs. We use tagged scenarios, so
that I can run a single relevant scenario (aka verify a specific node's
catalog) when making changes to a node specific module.
If you have many identical servers, you probably just want to verify the
catalog for each kind of server.
cheers,
Nikolay
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
