Re: version control

[Ed Brown]

We use CVS, as many sysadmins are already familiar with it, though it
has limitations and quirks.

In update.conf:
---------------
shellcommands:
   QA_policy_server::
        "/bin/sh -c 'cd /<policyrootdir> && umask 0002 && /usr/bin/cvs
-Q -d /var/CVS co <4 teams' modules>'" inform=false
--------------

By doing the 'cvs update' in update.conf, and by using a CVSROOT/loginfo
trigger that runs cfagent on commits, changes are effective immediately
after they are committed.  These steps are simplified by having the CVS
repository on the QA_policy_server.  Production servers are sync-ed from
the the QA server when ready.   

-Ed


On Mon, 2005-03-21 at 08:29, Jeff Sheltren wrote:
> On 3/20/05 10:11 PM, "Doug Chapman" <prjctgeek@gmail.com> wrote:
> 
> > The editfiles wiki page
> > (http://cfwiki.org/cfwiki/index.php/Editfiles_Examples) mentions using
> > version control on the cfengine config files.  How is everyone else
> > handling this?
> > 
> > My first idea was to use 'cvs export' to create a dated folder on the
> > policy server with all of the config files.
> > A symlink would point to the current version and could be changed
> > quickly for brute force rollbacks.
> > 
> > checkout command:
> > cvs export -r qa -d /var/cfengine/master-$(date +%s) cfengine/master
> > 
> > directory structure of /var/cfengine:
> > ...
> > inputs
> > master-1111384286
> > master-1111384164
> > master -> master-1111384286
> > modules
> > ...
> > 
> We use subversion.  All edits are done in a personal checkout, and then
> committed back to the subversion repository.  The server (cfservd) reads its
> files out of a directory which is nothing more than another checkout from
> the subversion repository.  This makes rollbacks easy since you can just cd
> into the cfservd directory and do a checkout of any working version you
> like.  This is where subversion's repository-wide versioning numbers are
> much nicer than CVS's per-file versions since it is easy to refer to a
> working 'snapshot'.
> 
> -Jeff
> 
> 
> 
> 
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-cfengine