I've been embedding the cookbooks/roles/data bags that are directly related to an application in the application repository itself, and using CI to update development environments (or organizations) at build time, then promoting through with asset revisions.
Adam
From: Sascha Bates <
">
>
Reply-To: " "> " < "> > Date: Saturday, January 26, 2013 10:14 PM To: " "> " < "> > Cc: Gourav Shah < "> > Subject: [chef] Re: Re: application builds/ci involving Chef Thanks. I'm in an environment where we use jenkins and maven for a lot of this at the moment. There's also some Vagrant/vbox in the mix as well as Eclipse/STS. I'm not looking for pointers so much as being interested in what others
have found to be successful.
One of the problems I see is that Chef code and Application code are decoupled: different repos, different teams managing collections of cookbooks, diverse environments. Dev teams don't think of Chef as part of the code base and I believe that this has led to some dysfunctional attitudes and behaviors. At the moment I'm noodling on methodology for introducing a tool like Chef that decouples configuration code from application logic. So I guess I'm maybe not looking for deployment solutions so much as wondering what people are doing to get their chef and app code working together and how it's working out for them. Sascha Bates |
">
| 612 850 0444 |
|
|
On 1/26/13 9:59 PM, Gourav Shah wrote:" type="cite"> |
Archive powered by MHonArc 2.6.16.