The cookbook supports the following installation methods:
- repo (default)
These plateforms have been tested successfully.
- Centos/RHEL 6 and 7 x86_64
- Ubuntu 12.04 and 14.04 amd64
- Smaller commits are better if we need to cherry pick.
- Make sure foodcritic runs without errors.
- Make sure 'knife cookbook test' runs without errors.
- Make sure 'kitchen test' runs without errors.
- Make sure 'rubocop' runs without errors.
- Write tests for your change.
Build and Release
For maintainers looking to release new versions of this cookbook you should follow this process:
- Add any
CHANGELOG.mdchanges with links to Pull Requests. Commit this to develop branch.
CHANGELOG.mdwith new version header and update diff links.
- Create a commit to then tag for release I would suggest something like this
git commit -am 'prep for v$MAJOR.$MINOR.$RELEASE release'. Commit this to develop and make sure that everything is good to go (ci passing and such).
- Push from develop to master:
git push origin develop:master
- checkout master branch and pull in changes:
git checkout master && git pull
- Create a tagged release:
hub release create v$MAJOR.$MINOR.$PATCHthis should prompt you in an editor to modify the tag message. I typically leave it default, but feel free to include any useful release notes.
- Use the
stovecommand to push the newly versioned cookbook to the supermarket:
stove --no-git. This assumes that you have installed
stove, properly configured authentication, and have been granted access to the supermarket.
- Optionally but recommended to update any associated PRs with a release link.