[chef] Re: Re: Re: Chef 11.8 Dependency Question

[John Keiser < >]

Another thing you can do is directly install chef 10.26.0 on your node--then minitest-handler will just pick that instead of jumping to 11.

As far as the compiling dependency, many folks won't hit that because they install chef with omnibus--no build tools involved, just install the .deb/.rpm/etc.

puma was chosen because it was the only webserver I could find that works everywhere Chef is supported (all Ruby versions and all platforms).  This included webrick (though I can't remember which platform/ruby version it failed on).  To see if I can help with this, I'll take another pass at finding a pure Ruby one with those characteristics, or some if statements I can use :)

On Fri, Nov 1, 2013 at 4:33 AM, David Petzel < " target="_blank"> > wrote:

Thanks Serdar,

Unfortunately, I don't think the Gemfile will help in this case, but let me give you a little more background on the CI process.

Upon commit to master  to a specific cookbooks git repo the following occurs:

- Cookbook source is uploaded to a dedicated testing org on the chef server

- A VM is launched and bootstrapped with 10.26.0 omnibus

- The run list will include the minitest-handler-cookbook, as well as the applicable test role/recipe that is specific to that cookbook.

- When it passes, its then uploaded to the prod org

So given that we are simply bootstrapping a 10.26.0 client and kicking off a run, I'm not clear how/where I'd introduce a Gemfile to my environment, but I'm happy to try it if you can let me know I'd do in my situation. 

From what I've been able to debug, I'd be surprised if others are not seeing this issue as the dependency issues seems to be come from upstream (unless of course folks make it a standard practice to have build tools on their CI nodes)?

On Thu, Oct 31, 2013 at 11:58 PM, Serdar Sutay < " target="_blank"> > wrote:

Looks like minitest-chef-handler has below dependency on Chef: 

  gem.add_dependency('chef', '>= 10.12.0')







If you have a Gemfile by which you are controlling your environment you can add:







gem 'chef', '~>10.26'







to it which should move you to Chef 10 and will resolve the issue. 




Hope this helps. If not, it would help if you can give a little bit more details about your CI process of testing cookbooks.