I have often come across interesting Vagrant setups for testing components. The original source repo for this project - https://github.com/L2G/duckpan-vagrant - was one such example. (Another example was redis-failover-test which I was playing with and fixed some issues on: https://github.com/swhitt/redis-failover-test/pull/2 ) However, I often find these Vagrantfiles extremely fragile and broken.
I have been looking to see if it might be possible to use TravisCI or similar to perform CI on Vagrantfiles.
Since CircleCI is based on LXC, I thought they might be a potential alternative that could work, but apparently this is outside of their capabilities at present, as well: https://twitter.com/shedd/status/400823678448844801
I have often come across interesting Vagrant setups for testing components. The original source repo for this project - https://github.com/L2G/duckpan-vagrant - was one such example. (Another example was redis-failover-test which I was playing with and fixed some issues on: https://github.com/swhitt/redis-failover-test/pull/2 ) However, I often find these Vagrantfiles extremely fragile and broken.
I have been looking to see if it might be possible to use TravisCI or similar to perform CI on Vagrantfiles.
Unfortunately, that doesn't appear to be possible currently: http://omerkatz.com/blog/2013/6/15/travis-ci-does-not-work-when-you-package-vagrant-boxes-as-a-build-step-yet
Since CircleCI is based on LXC, I thought they might be a potential alternative that could work, but apparently this is outside of their capabilities at present, as well: https://twitter.com/shedd/status/400823678448844801
To really get this setup, one option seems to be a (apparently buggy & nascent) Jenkins plugin: https://wiki.jenkins-ci.org/display/JENKINS/Vagrant+Plugin