> On Thu, Jun 17, 2010 at 4:23 PM, PBWebGuy <[email protected]> wrote: >> I was just looking over your puppet-puppet recipe and I was curious on >> how you are managing your different target environments. I see that >> you have defined different trees for each environment: >> ... >> So I am assuming that you must need to maintain 3 different trees of >> code for all of your classes? What I am trying to do is avoid that >> but am concerned about edits of classes, etc that can trickle out to >> production before they have been properly QA'd. I haven't read much >> on how best to do this and have been working on a completely different >> approach. I would be interested in how you are handling that.
My actual usage gets a bit more complicated, but as Nigel suggested, I generally have a single repository of code and each environment represents a different point in time "snapshot" of that codebase. All my changes are checked in to 'development'. When I'm happy that the dev codebase is fairly stable, I'll then copy/tag that codebase, which can be checked out to the 'testing' environment. If that codebase performs as expected, then it gets checked out to production. Im currently using SVN, so this fairly trivial to do - just create a 'cheap copy' of the current repo and tag it with an appropriate name (based on release version / date for me) Hope that helps, Cheers, Bryan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
