- From: Kirill Timofeev <
>
- To: "
" <
>
- Subject: [chef] deployment and rollback of cookbooks, roles, environments and data bags
- Date: Mon, 20 May 2013 10:29:36 -0700
Folks,
currently we have all chef stuff (cookbooks) in git repository.
Post-commit hook triggers jenkins job, which updates chef using slightly
modified version of chef-jenkins synchronization tool. Unfortunately
this approach allows submission of broken code, which would be revealed
only while pushing changes to chef-server. I want to modify this
approach by utilizing update hook and accepting changes only if they
would be successfully uploaded to chef server. But in order to do this I
also need some rollback mechanism on chef-server side to discard update
in case of any issues.
So my question is: do we have in chef server 11.08 any built in
mechanism for transactional updates or I need to implement some custom
solution?
Thanks,
Kirill.
- [chef] deployment and rollback of cookbooks, roles, environments and data bags, Kirill Timofeev, 05/20/2013
Archive powered by MHonArc 2.6.16.