Matt, This is an interesting approach - food for thought. Do you find yourself standing up test classes in the alpha/beta versions of your files and removing them when you're ready to tag them as prod?
Maybe I'm not approaching the problem the right way by thinking of test environments as sandboxes that are more or less permanent. We have test machines for most of the services we provide, so I sort of assumed I'd build test classes for each service based on those - but maybe I'm shooting myself in the foot by marrying the concepts of service testing and Cfengine testing..... -Jess On Thu, Mar 4, 2010 at 12:01 PM, Matt Richards <defraya...@gmail.com> wrote: > Mine is similar to how Neil does it. I use plain old CVS. Specifying tags > on the cf configuration to indicate which level (alpha, beta, prod, etc...) > the edit should be in: > > cvs tag -F alpha failsafe.cf > > I then can key off the tag to release different levels and release using > cvs. Something like the following: > > cvs -Q export -r alpha -d /cfengine3-alpha <cvshead>/client > > You can see which release is staged for each file: > > cvs status -v failsafe.cf > =================================================================== > File: failsafe.cf Status: Up-to-date > > Working revision: 1.16 Tue Jan 12 12:55:34 2010 > Repository revision: 1.16 XXXXX/failsafe.cf,v > Sticky Tag: (none) > Sticky Date: (none) > Sticky Options: (none) > > Existing Tags: > alpha (revision: 1.16) > beta (revision: 1.14) > prod (revision: 1.16) > start (revision: 1.1.1.1) > XXX (branch: 1.1.1) > > I like it, simple, effective, all the configs are in one place. > > > > On Mar 4, 2010, at 11:45 AM, Jessica Greer wrote: > > Anyone want to share advice on using SCM/revision control software to > manage Cfengine configuration? > > I've recently joined a group where several people will be editing inputs > and masterfiles, and it'll be important to have a clear picture of what > changes have been made and by whom. > > Yale is using Bazaar for several other projects, so if anyone has feedback > on Cfe+bzr, I'd be especially interested. > > Thanks as always, > -Jess > > ------------------------- > Jessica Greer > Unix Infrastructure and Virtualization > Information Technology Services | Yale University > (203)436-5205 | jessica.gr...@yale.edu > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine > > > -- ------------------------- Jessica Greer Unix Infrastructure and Virtualization Information Technology Services | Yale University (203)436-5205 | jessica.gr...@yale.edu
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
