- From: Seth Chisamore <
>
- To: "<
>" <
>
- Subject: [chef] Re: My Wishlist: Better Chef-Solo Support
- Date: Wed, 20 Feb 2013 19:48:29 +0000
- Accept-language: en-US
On Feb 20, 2013, at 1:47 PM, Julian C. Dunn
<
>
wrote:
>
It does drive me crazy when cookbook authors require Chef Server
>
functionality to accomplish basic tasks. For instance, we've forked &
>
modified the Jenkins cookbook significantly because of its assumption that
>
you can query for the node with the Jenkins master role to retrieve the SSH
>
key.
Opscode is taking over maintenance of this cookbook and I will be making sure
things operate as expected in a solo-based environment…mainly because we do
development in Vagrant/Berkshelf and testing in Test Kitchen. The code will
now live at:
https://github.com/opscode-cookbooks/jenkins
Until the new 1.0.0 version of the cookbook is released I believe you can get
around your issue [1] by explicitly setting the following attributes:
node.set['jenkins']['server']['pubkey']
--
Seth Chisamore
Software Development Engineer, Opscode, Inc.
IRC, Skype, Twitter, Github: schisamo
[1] -
https://github.com/heavywater/chef-jenkins/blob/develop/recipes/node_ssh.rb#L24
Archive powered by MHonArc 2.6.16.