Here’s and example of how we do it in Jenkins. It’s worked out wondrously.
On May 17, 2014, at 14:52, “Daniel DeLeo” <firstname.lastname@example.org:email@example.com> wrote:
On Saturday, May 17, 2014 at 2:33 PM, Lamont Granquist wrote:
if you run chef-client out of the chefdk path, doesn’t chef_gem install
into the embedded ruby?
that might go into the ~/.chefdk directory of the user installing it
though so might not be ideal if you run it as root (not sure…)
On 5/17/14, 4:47 AM, Steffen Gebert wrote:
In regard to that:
I am actually wondering if someone […] implement resources like
The simplest thing you can do is add the
--no-user option to the install, which will install to the embedded gem path instead of the user gem path. It does feel a bit wrong, but we haven’t observed any issues doing this with chef-client omnibus installs so it should be okay.