[chef] Re: ChefDK and CI

[Paul C < >]

Jay,  I  am struggling with this problem as well.    At first I started converting everything in CI to use ChefDK but was having problems, so I'm back looking for a suitable compromise that would allow for identical results in both chefdk and CI environments.   I'd love to hear how other people are handling it.

On Fri, Oct 10, 2014 at 7:43 AM, JayP < " target="_blank"> > wrote:

Ohai Chefs!

We are trying to get more of our team to use ChefDK for their cookbook
development.  If everyone is using ChefDK is it recommended to use ChefDK on
your CI Server agents as well to do the testing of your cookbooks?  All our
repositories have a Gemfile which have some duplicate gems so it wouldn't be
required but my worry is that someone will be using chefdk locally and
potentially see different results in CI.  We are managing our CI agents via
chef so that would mean the chef-client that comes with ChefDK would be used to
provision the host with other things such as vagrant, virtualbox, rbenv, etc.
If folks think it is low risk to use the chef gem for CI instead of ChefDK I
think I prefer that route as it makes it easier to upgrade itself etc.  What
are folks thoughts on this?  I guess this is the case for any users creating
community cookbooks and testing via travis.  Opinions welcome.

Thanks,
Jay