The core idea of the cookbook is to be a "one-stop-shop" to build a cookbook testing pipeline. It is an effort to define the Chef Resources to simplify the use of Jenkins CI for Chef cookbook development. Originally forked from cooking-with-jenkins - see the accompanying blog post for details and commentary. Additional inspiration came from David Schlenk's fork of the project called jenkins-cookbook-ci.
- Ubuntu 14.04
- Vagrant
- VirtualBox
- Test Kitchen
- rbenv
- ruby 2.1.2
The quick and dirty launch to use: bundle exec kitchen converge
When Vagrant finishes provisioning the machine, Jenkins will be available on http://localhost:8080/.
Known Issues:
-
The machine creates test jobs for two cookbooks, and the first test run for each (during provisioning) will fail. I suspect this would be fixed by restarting Jenkins after adding plugins (the "configure-jenkins" recipe) and before defining the jobs, but it didn't bother me enough to add the necessary hackery.
Click "Build Now" on each job and you'll see them work correctly.
-
The docker recipe needs some additional work. There have been some great advances in docker's upstream cookbook, and I have not had time to make proper adjustments.
- Zachary Stevens (zts@cryptocracy.com)
- David Schlenk (david.schlenk@spanlink.com)
- Brian E Clow (bclow-github@temporalflux.org)