On Tue, Oct 18, 2011 at 01:52:18AM -0700, Andreas Paul wrote:
> we are currently managing our puppet modules with one SVN workspace for each
> admin.
> The post commit hook script updates /etc/puppet/ directory and triggers the
> puppet kick of the correct server.
we use git branches. the master
I use two separate puppetmasters for lab and production. (The lab side has more
of the "dratted commas" style of checkin.)
Testing changes to one particular type of server is where virtualization really
shines. You can spin up a scratch virtual machine with the same manifests as
your target hos
I had a similar problem, i use Git, and i though i could use branches and
Git tricks, but it does not mixes well with Puppet environments. What i do
below permits to use many puppet code branches, while having my puppetmaster
serve all different branches at the same time using environments
In my c
Hi,
we are currently managing our puppet modules with one SVN workspace for each
admin.
The post commit hook script updates /etc/puppet/ directory and triggers the
puppet kick of the correct server.
The problem we have with this solution is that sometimes there are many
small checkins to one c
