https://github.com/ashwanthkumar/kitchen-bento-setup
Vagrant setup to create a box for using with test-kitchen
https://github.com/ashwanthkumar/kitchen-bento-setup
Last synced: 8 months ago
JSON representation
Vagrant setup to create a box for using with test-kitchen
- Host: GitHub
- URL: https://github.com/ashwanthkumar/kitchen-bento-setup
- Owner: ashwanthkumar
- License: apache-2.0
- Created: 2015-08-30T18:09:07.000Z (almost 11 years ago)
- Default Branch: master
- Last Pushed: 2015-09-03T07:16:10.000Z (almost 11 years ago)
- Last Synced: 2024-12-27T12:44:50.355Z (over 1 year ago)
- Language: Shell
- Size: 109 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Kitchen Bento Setup
This is out of frustration with [mitchellh/vagrant#5492](https://github.com/mitchellh/vagrant/issues/5492). This setup helps you get the base CentOS 6.6 box from Opscode install custom stuff and re-package it for using them with KitchenCI. For some unknown reasons running `vagrant package` works but re-packaging after that doesn't seem to work. This is an attempt at automating that and also provides clear visibility on what all gets pre-installed in the test environment that needs attention on the production machines.
## To build the box
Since we run all our setup as part of provisioning process, it is enough if you just do `vagrant up`. For convience I've also added `build.sh` which looks for any existing VMs, destroy them and launches a new one and creates a `opscode-centos-66-v${VERSION}.box` file. `VERSION` is from VERSION file.
Everytime you make some changes please run `release.sh`. It builds and increments the VERSION file.
### NOTE
I would love to use Packer for this, but [mitchellh/packer#869](https://github.com/mitchellh/packer/issues/869) prevents me :(