Use Jenkins to drive continuous deployment and synchronization of your Chef Environments from a git repository
# You should always be within a chef-repo when you use chef-jenkins! (we are, after all, going to get run from jenkins - but see that later on)
# To syncronize a git repository with a chef server - the branch is master by default. # You must provide an environment to pin to, which will always be current $ chef-jenkins sync –env-to dev
# Propogate the cookbook policy from one environment and make it the policy for another environment $ chef-jenkins prop –env-from dev –env-to qa
# Use a config file $ chef-jenkins prop –config ~/chef-jenkins.rb –env-from dev –env-to qa
# Use the default config file - jenkins.rb $ chef-jenkins prop/sync
-
Check out the latest master to make sure the feature hasn’t been implemented or the bug hasn’t been fixed yet
-
Check out the issue tracker to make sure someone already hasn’t requested it and/or contributed it
-
Fork the project
-
Start a feature/bugfix branch
-
Commit and push until you are happy with your contribution
-
Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.
-
Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
Copyright © 2011 Opscode, Inc. See LICENSE.txt for further details.