I use Hudson.
I've used Test::Unit to wrap validations of generated config files in
the past. I want to know as early as possible if something isn't
going to work.
Functionally testing the config from the outside in might be easy but
slow. You can deploy to a VM and actually test it using the
I've been thinking about using Hudson for this, so its good to know that
there are others out there doing this.
3 projects that I've bookmarked to look at for unit testing frameworks
for the OS are:
https://fedoraproject.org/wiki/AutoQA
http://autotest.kernel.org/
http://www.linux-kvm.org/page
On Sun, Nov 8, 2009 at 1:12 AM, Douglas Garstang
wrote:
> I need to both make sure that the base directory exists AND the
> symlink to it exists. Other than defining a file resource that ensures
> the base directory exists and another file resource to create the
> symlink, how else could this be
I set up puppet for the first time yesterday, on two Solaris 10
machines, each running puppet v0.24.7. I made a modified version of
the initial manifest described in
http://reductivelabs.com/trac/puppet/wiki/InstallationGuide (updating
/etc/passwd, sudoers doesn't exist in Solaris). Things work fi