[chef] Re: Re: Managing a chef repository with multiple engineers

[John Alberts < >]

Wow, 5 minutes and 4 replies.  Awesome community. :)

Already using the awesome knife-spork plugin, but I'll take a look at the slides and also the youtube video and reply back afterwords.

Thanks

John

On Mon, May 6, 2013 at 3:16 PM, Daniel Schauenberg < " target="_blank"> > wrote:

Hi John,

we are using knife-spork to manage our Chef workflow at Etsy and these
slides[1] should give a rough overview how we do it. Hope that helps, if you
have any questions, let me know.

Cheers,
Daniel

[1]: https://speakerdeck.com/mrtazz/chef-workflow-at-etsy

On Mon, May 06, 2013 at 03:09:47PM -0500, 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.
>   John

--
John Alberts