RE: [Infrastructures] Change Control and cfengine

[Heilke, Rainer]

We are doing essentially what you are planning. We have a development
directory where we work on changes, etc. The files are commit'ed using a
Perl script (built long before any of us got here) accessing CVS and
requiring comments to the changes. Then, using another Perl script, the
changes get pushed out using another CVS mechanism to a production
directory. 

Rainer

> -----Original Message-----
> From: Dennis, Richard [mailto:Richard.Dennis@lehman.com] 
> Sent: Friday, April 18, 2003 1:29 PM
> To: help-cfengine@gnu.org; infrastructures@roton.terraluna.org
> Subject: [Infrastructures] Change Control and cfengine
> 
> 
> Thanks for replies to my earlier post on splitting cfengine 
> config files.
> Here's another question I forgot to post.  
> 
> What's the best way to handle the change control process and 
> cfengine?  I'm
> curious what's the best way to protect your environment (and CYA) when
> updating configs.
> 
> What I've decided to do to keep a /var/cfengine/stage and 
> /var/cfengine/prod
> directories, each with an inputs and files subdirectories.  
> Both directories
> contain checked out copies of a CVS repository.  I'm working on a perl
> script that will automate the CVS tagging of the stage 
> directory, so only
> when the a change is approved, the prod directory will 
> checkout the updated
> tagged version of the repository.
> 
> Just seems to me that change control is an integral part to file
> distribution, and I'm curious to know how others handle this.  
> 
> Again, TIA.
> 
> --Rick
> 
> --------------------------------------------------------------
> ----------------
> This message is intended only for the personal and 
> confidential use of the designated recipient(s) named above.  
> If you are not the intended recipient of this message you are 
> hereby notified that any review, dissemination, distribution 
> or copying of this message is strictly prohibited.  This 
> communication is for information purposes only and should not 
> be regarded as an offer to sell or as a solicitation of an 
> offer to buy any financial product, an official confirmation 
> of any transaction, or as an official statement of Lehman 
> Brothers.  Email transmission cannot be guaranteed to be 
> secure or error-free.  Therefore, we do not represent that 
> this information is complete or accurate and it should not be 
> relied upon as such.  All information is subject to change 
> without notice.
> 
> 
> _______________________________________________
> Infrastructures mailing list
> Infrastructures@mailman.terraluna.org
> http://mailman.terraluna.org/mailman/listinfo/infrastructures
>