[chef] Re: Best practices for keeping repo and server sync'd

[Vladimir Girnet < >]

You can also use CI tools like Jenkins to monitor SCM changes and publish everything required to chef-server. 

We do have two shell build steps:

 - knife cookbook test -a -o cookbooks/

 - knife cookbook upload -a -o cookbooks/

First one is re-testing cookbooks syntax, second is uploading all cookbooks to server. This way we ensure that syntax is correct, and chef-server always have cookbooks from repo, even if someone accidentally uploaded a cookbook manually. 

On Apr 6, 2012, at 8:09 AM, < "> > < "> > wrote:

hello,

guard-knife seems very interesting.

As the initial sender of this post, we are using subversion, and we have a
small bash script like this

cd /root/svnChef/trunk
svn update
# TODO: Backup cookbooks
knife cookbook upload -a

We are never uploading a cookbook directly to the server, all the cookbook
changes has to go through subversion commit.

By the way, is there a way for exporting all cookbooks from the server, such
knife cookbook export -a, please ?
That's what we would like to do for replacing '# TODO: Backup cookbooks'

Best regards,
Christophe

--
Vladimir Girnet
Infrastructure Engineer
Tacit Knowledge
http://www.tacitknowledge.com