I just started a blog, and my first post is on this topic. It’s a reasonable summary of the Berkshelf approach (including the link to Jamie’s talk that Noah posted and some other resources), and some things to take in to consideration. We are just starting down this path, so we don’t have it all figured out quite yet…
Also, this episode of the FoodFightShow, which has Etsy and Riot Games both discussing how they handle cookbook collaboration:
I hope this is helpful!
Senior Systems Engineer
Alert Logic, Inc.
[ C.H.A.M.S. - Culture, HUGS, Automation, Metrics, and Sharing ]
On May 6, 2013, at 3:09 PM, John Alberts wrote:
I’m wondering if anyone has come across any blog posts or anything regarding best practices with managing the cookbooks in a chef repository when you have multiple engineers working with the repository at the same time?
Currently, I’m basically using the git-flow approach; however, I find it cumbersome to merge multiple feature branches together for different cookbooks (and sometimes the same cookbook), make sure there is an appropriate version bump in each affected cookbook, updated changelog files in each cookbook, and determine what actually changed so that I can upload the changed cookbooks, roles, data bags to the server.
I’m just wondering what other folks are doing.