Hi Eric,
thanks for starting this interesting thread!
On 6/25/2010 1:02 AM, Eric Sorenson wrote:
- Describe revision control setup subversion server with a branch
named 'test' and a branch named 'prod'. all puppetmasters live on the
prod branch - $moduledir is a working-copy checkout of svn, and one
puppetmaster in each env has a second server running on :8141 that
lives on the test branch. prod branch commits should only be 'svn
merge's of commits in test but this isn't enforced by technological
control. Post-commit hook sends out mail with the diff to everyone
on the team.
Is there a specific reason you're not using real environments?
- What are you doing to improve/change the setup? Pre-commit hook to
do syntax checking on files to refuse commits on blatant errors
Contemplating a post-commit push to 'svn up' the puppetmasters but
not sure if this is really a good idea
Guess that depends on the quality of your checkins.
Need some auditing between the
branches to see what changes are not yet merged or if prod has
somehow diverged (non-merge changes on the branch) Maybe one/handful
of clients per class of host ought to live pointed at the test
server.
This would also reduce the danger of automatically svn ups.
How are you handling "breaking" changes which shall be done in
maintenance windows and/or "rolling upgrades"?
Best Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
