This cookbook install jenkins and test-kitchen for chef CI.

####test-kitchen Test Kitchen is a test harness tool to execute your configured code on one or more platforms in isolation. A driver plugin architecture is used which lets you run your code on various cloud providers and virtualization technologies such as Amazon EC2, Blue Box, CloudStack, Digital Ocean, Rackspace, OpenStack, Vagrant, Docker, LXC containers, and more. Many testing frameworks are already supported out of the box including Bats, shUnit2, RSpec, Serverspec.

• apt - https://github.com/opscode-cookbooks/apt
• yum-epel - https://github.com/opscode-cookbooks/yum-epel
• yum-repoforge - https://github.com/opscode-cookbooks/yum-repoforge
• jenkins - https://github.com/opscode-cookbooks/jenkins
• java - https://github.com/agileorbit-cookbooks/java
• virtualbox - https://github.com/psyreactor/virtualbox-cookbook
• vagrant - https://github.com/psyreactor/vagrant-cookbook
• ruby_build - https://github.com/fnichol/chef-ruby_build
• docker - https://github.com/bflad/chef-docker
• sudo - https://github.com/opscode-cookbooks/sudo
• sysctl - https://github.com/onehealth-cookbooks/sysctl

The following platforms and versions are tested and supported using Opscode's test-kitchen.

• CentOS 5.8, 6.3
• Ubunutu 12.04
• Debian 7.2

The following platform families are supported in the code, and are assumed to work based on the successful testing on CentOS.

• Red Hat (rhel)
• Fedora
• Amazon Linux

Include jenkins_kitchen in your node's run_list:

"default_attributes": {
  "jenkins_kitchen": {
    "driver": "docker"
    }
  }

1. Fork the repository on Github
2. Create a named feature branch (like add_component_x)
3. Write your change
4. Write tests for your change (if applicable)
5. Run the tests, ensuring they all pass
6. Submit a Pull Request using Github

More details

Authors: Lucas Mariani (Psyreactor)

• [email protected]
• https://github.com/psyreactor