Forum: CFEngine Help Subject: Re: avoiding double-runs to converge when using template operations Author: jgreer Link to topic: https://cfengine.com/forum/read.php?3,27428,27471#msg-27471
/var/cfengine/masterfiles on our server is a working copy of a single subversion repository (with externals to another shared Yale repository we use to share code to other groups here using CFEngine). That includes inputs as well as file content managed by CFEngine. Nothing surprising or crazy going on - we don't even (at this point) automatically update out of version control. The basic workflow goes like this: 1. I make changes in a personal working copy to policy and managed files (This working copy is sometimes /var/cfengine/masterfiles on a sandbox machine, which is configured to point to localhost for policy). 2. I vet changes personally and send diff to my team 3. Team views diff and provides feedback on proposed changes 4. I incorporate feedback into my working copy and commit changes to subversion 5. During times our agents are NOT phoning home to the master, I go to the working copy in /var/cfengine/masterfiles on the server, reverse-diff to show the changes coming down the pike, confirm I see what I expect and nothing more, and svn up, and document the final changeset for team records _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
