I am setting up a new workflow myself, it will be as follows: One git repo for modules and manifests, a second for hiera. Branches are for features and personal development branches. I might install forge repositories in a different modulepath to force working with the community.
The git repository goes through gerrit and all commits are automatically check checked for syntax or lint errors by jenkins before they are merged. All modules updates might also require a visual code-review, don't know yet. Different environments (development, staging, etc) are represented using an extra hiera lookup level and are also reflected in the node to modules mapping thats in place. This is what works for us. Jos On Monday, May 28, 2012 3:14:54 PM UTC+2, Andy Taylor wrote: > > I'm currently trying to work out the best way structure my Puppet > environments and VCS structure. At the moment I'mk working on > something like this: > > Three Git repositories (one for modules, one for Hiera, one for node > manifests) > Multiple branches (each branch representing an environment, e.g. > production, dev, testing etc.) > > When changes to modules/Hiera are made, the changes will be made to a > testing branch, and then merged up the branches until it hits > production (with the appropriate testing of course). So something like > this: > > unstable > dev > testing > production > > What system do you guys use? Any suggestions about the above workflow? > > Thanks! > > Andy > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/03LLU2p-mvMJ. 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.
