On Wed, Dec 2, 2009 at 9:51 AM, Nigel Kersten <nig...@google.com> wrote:
> Yep. It's the provider forcing stuff that is the problem. I was going > to start digging in to work out what's a real alarm and what isn't. > > How are you using this Ohad? Are you running it on your servers? > > Currently we've created a list of "common" node types with various classes and parameters - which will be executed based on a repo hook. another usage is that a person which is developing a manifest, will run this test on a few basic node file, to filter out any programming error - similar to the way some puppet use --parseonly. I'm considering running it in some sort repo hook when committing, but not sure how good of an idea it would be. > I'm thinking of moving one of my test servers to collect the cached > node info for all my clients and continuously run manitest against the > development code for my environments, perhaps triggered by changelist > submissions to my VCS. > > That's probably a good idea (but), usually the problem I have is not on existing node setup, rather that someone will add one more class to its host manifest and then everything breaks.. I'm happy you find it useful! cheers, Ohad -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
