- From: Daniel Schauenberg <
>
- To:
- Subject: [chef] Re: Managing a chef repository with multiple engineers
- Date: Mon, 6 May 2013 22:16:20 +0200
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
Archive powered by MHonArc 2.6.16.