Hi there, Is there a canonical way to manage my recipes' release process ? I mean test it before they're pushed in production.
For the moment we only have 1 puppetmaster here. I noticed that if I have a syntax error in one of my included .pp, then puppet runs fail on all nodes (even if they do not use this recipe), which is not acceptable. More generally, working directly on production recipes seems too riskee, since people who will manage those recipes are not devs but sysadmins, which means poor development skills (and no versionning for the moment). I found the documentation about puppet "environments" ( http://docs.puppetlabs.com/guides/environment.html ) : does anybody use it here ? I also read some of you have 2 puppetmasters running on different ports, for test and prod : how do you do that (init scripts available somewhere? different conf/manifests directories? sync between test and prod?). Do you have a pool of client machines dedicated to your tests ? Do you handle this kind of problems directly with your version control system (post hooks?), or maybe at an other level in your external node provider ? I was not able to find much information about that, but don't hesitate to redirect me to an article or a thread here if it has already been discussed. Thank you, Cheers, -- Jean-Baptiste -- 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.
