- From: Clif Smith <
>
- To:
- Subject: [chef] Managing multiple discrete projects
- Date: Tue, 15 Oct 2013 21:45:31 -0500
We've been using Chef for a couple of years now and love it. Thankfully our
business is growing to the point where it's becoming a bit onerous to support
multiple products with 1 Chef repo in 1 Git repo. For example, we're
currently supporting 2 products. When we update a cookbook, data bag, etc.
that's used by both products, we should always test that those changes don't
cause any issues. So far that's been fine, but this latest product is
causing many changes throughout my chef repo and the overhead in testing
across 3 products is a bit more than we'd like to take on. We're pondering
standing up a couple more Chef servers (prod/non-prod) and utilizing a copy
of the current git repo but I hate the idea of enhancements not easily making
it into the other repo(s). We're also looking at a git repo for common
artifacts which would alleviate some of my worries.
Having said all of that…how are others handling similar situations?
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
- [chef] Managing multiple discrete projects, Clif Smith, 10/15/2013
Archive powered by MHonArc 2.6.16.