Setting up a custom RubyGems Repository for Chef in Test Kitchen

If you work in an Enterprise, you likely have guidelines around where your dependencies can be stored. Alternatively, you may have proprietary dependencies that you want to store privately.

Although you may have set up your Chef Client to use your private RubyGems repo, that will not work when you're running through Test Kitchen because it sets up its own Chef configuration.

To resolve this, update your $HOME/.kitchen/config.yml or your .kitchen.yml with the following addition to the provisioner block:

 provisioner:
   name: chef_zero
+  client_rb:
+    rubygems_url: 'https://private.rubygems-repo.com/something/gems'

Written by Jamie Tanna's profile image Jamie Tanna on , and last updated on .

Content for this article is shared under the terms of the Creative Commons Attribution Non Commercial Share Alike 4.0 International, and code is shared under the Apache License 2.0.

Tags

This post was filed under articles.

Related Posts

Other posts you may be interested in:

Interactions with this post

Interactions with this post

Below you can find the interactions that this page has had using WebMention.

Have you written a response to this post? Let me know the URL:

Do you not have a website set up with WebMention capabilities? You can use Comment Parade.