It may be worth using git just to be able to use berkshelf. Look at svn2git to mirror your changes to svn.
Sent from my iPhone On Oct 24, 2014, at 4:18 PM, Fouts, Chris <
">
> wrote:
Since we use SVN and not git, Berkshefl can’t help me.
From: Dave Kichler [
">mailto:
]
Sent: Friday, October 24, 2014 5:21 PM
To:
">
Subject: [chef] Re: Jenkins and Chef
Are you using any sort of cookbook dependency management tool? (Berkshelf, librarian, etc) If not, it sounds like adopting one of those tools and installing/using it on Jenkins would greatly simplify your workflow.
On Fri, Oct 24, 2014 at 1:59 PM, Fouts, Chris <
" target="_blank">
> wrote:
I’m trying to setup my existing RHEL Jenkins build slaves to orchestrate deploying and installing our product on multiple servers. I have a set of Jenkins jobs that deploy ProdA,
and then a different, but similar, set of Jenkins jobs deploy ProdB. Both Jenkins job sets “can” be running on the “same” build slave. However, ProdA may require a different set of cookbooks that ProdB. Therefore, my solution is to checkout the corresponding
set of cookbooks for ProdA and ProdB, and since each job set runs on a different Jenkins $WORKSPACE directory, my cookbooks directory locations do not clash. I can then have the Jenkins jobs upload their cookbooks to the server – so far so good.
However, how do I orchestrate my knife.rb file to point to the corresponding cookbook_path? Remember I’m doing two Jenkins job sets on the “same” build slave, meaning I’ll have
one .chef/knife.rb file at any one time. I’m aware of the knife block plugin
Make sense?
Chris
|