tree: d39e7ab6b8b1c1696431ab07061627d4ab85f44d [path history] [tgz]
  1. .gitignore
  2. README.md
  3. Vagrantfile
  4. init.sh
  5. local-ci.sh
vagrant/README.md

Vagrant VM for CI and debugging

Running vagrant up master will bring up an environment similar to the one used by Travis for CI. If the build fails, it can be inspected by entering the machine with vagrant ssh master. When you're down with the VM, you can clean up with vagrant destroy -f.

The advantage of this is you don't need to worry about the potential environment pollution, and others can reproduce the results from other platforms.