We are working internally to come up with some regressions, if it turns out
to usable I'll be more than happy to share.
If you get to a stage hudson is working - let us know :)

Ohad

On Wed, Dec 2, 2009 at 4:17 AM, Nicolas Szalay <nsza...@qualigaz.com> wrote:

> Tried it out and did a bunch of debugging with ohad. Works really fine, I
> planned to check all manifests but I still not decided how to do it on a
> continous basis. I have to take a look at hudson.
>
> Nicolas.
>
> ----- Mail Original -----
> De: "Nigel Kersten" <nig...@google.com>
> À: puppet-users@googlegroups.com
> Envoyé: Mardi 1 Décembre 2009 19:47:38 GMT +01:00 Amsterdam / Berlin /
> Berne / Rome / Stockholm / Vienne
> Objet: Re: [Puppet Users] manitest - a simple tool to help your puppet
>  development and testing
>
> On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy <ohadl...@gmail.com> wrote:
> > If it happened to you before that someone broke your manifest because of
> > simple change (e.g. didnt test it on all hosts/classes external nodes ...
> > combinations) this tool might be useful for you.
>
> No-one else tried this out? It's really quite cool.
>
> Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired
> there. We actually serve our manifests out of a different location, so
> I had to do a minor tweak to get that working.
>
> It's a shame we can't impersonate architectures though... I'd love to
> be able to simulate catalog runs of a Mac client on a Linux continuous
> build server.
>
>
>
> >
> > the idea is very simple, just try to compile the manifest based on
> > customized facts, classes, environments and external nodes parameters (if
> > you use it) .
> > You need to run this script only were you develop your manifests (e.g.
> your
> > puppetmaster), there is no need to try out a puppet run on each and every
> > system type that you have.
> >
> > You might also find it useful to run this script in some sort of a cron
> or
> > via a repo hook, to find out any broken manifests running around..
> >
> > This script was originally written by a colleague of mine (Paul Kelly),
> > however, I've adjusted it to hopefully common usage.
> >
> > Its brand new, so any comments / improvements (which I'm sure there are
> > plenty) are welcomed.
> >
> > Hopefully you'll find it useful,
> > Ohad
> >
> > http://github.com/ohadlevy/manitest
> >
> > --
> >
> > 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<puppet-users%2bunsubscr...@googlegroups.com>
> .
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en.
> >
>
>
>
> --
> nigel
>
> --
>
> 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<puppet-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
> --
>
> 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<puppet-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
>

--

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.


Reply via email to