On Thu, Sep 01, 2011 at 11:58:04AM -0700, Russell Van Tassell wrote: > I'm currently in the same position, and the solution I've proposed (and am > currently working on) involves using a central repository (likely git). The > puppet client (running on the master) simply checks the current master > branch on the remote repository -- if the revisions are not the same, it > just pulls a new copy.
Once your organisation grows you want some release management: in GIT: - everybody has a local Git - all work is done in new branches - all finished branches are pushed back to a central GIT - the releasemanager mergens everything, and does testing (either by looking or running a test suite) - after testing has finished a tag is applied - the tag is checked out on the puppetmaster(s) -- __________________________________________________ "Nothing is as subjective as reality" Reinoud van Leeuwen reinou...@n.leeuwen.net http://reinoud.van.leeuwen.net kvk 27320762 __________________________________________________ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
