On Monday, June 18, 2012 at 1:07 PM, Jo Rhett wrote: > *boggle* Um, so your configuration management system is not part of your > change management implementation? That's what you just said, and it makes no > sense.
Jo, Not to speak for David but in general - the point is that they are different components of an interlocking whole. In the cases you are discussing (conflict between multiple groups working on related systems) you need to implement better change control or CI. While Puppet works quite well with those technologies, we don't yet provide tooling around git/svn/choose your tool VCS, nor do we provide the workflow itself. In terms of conflicting changes, you really need code review, CI, or preferably both. That's how large organizations handle scale. Trying to force the tool to solve development problems isn't going to work. Look at how development teams solve the same problems. They don't do it by refusing to build a new daily snapshot of parts of the software. -- Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
