GIT to manage cookbooks

[spuder]

smuckers see this example here:

We use gitlab-ci. Every time a change is pushed to the master branch of a cookbook, gitlab-ci basically runs a berks install and a berks upload. To release a new cookbook, all we have to do is change the version inside the metadata.rb and merge to master.

This only works if you are able to use protected branches (which gitlab-ci supports).

Syncing Chef Server with external Git Repo

Here is an example where the chef key file is stored on a ci server, and each cookbook has a .berkshelf directory that contains a json file with the config of which chef servers to upload to. Assuming you are using something like jenkins, team city, gitlab -ci that integrates with your version git server. Te following script would be configured to only run on merge to master, or every time a git tag is created. - rm -f Berksfile.lock - echo "$LAB_CHEF_KEY" > "/foobar/private-key.pem" - berks i…