title: How to combine Vagrant with Jenkins for the perfect Continuous Integration Environment?
body: <p>You have a project which has got some SW requirements to run (e.g.: a specific version of Apache, a version of PHP, an instance of a MySQL database and a couple of other pieces of software).</p>
  
  <p>You have already discovered <a href="http://vagrantup.com/docs/getting-started/why.html" rel="noreferrer">Vagrant</a>, so your virtual environment is all setup. You can create boxes out of your configuration files and cookbooks.</p>
  
  <p>You have also understood the advantages of a Continuous Integration system such as <a href="http://jenkins-ci.org/" rel="noreferrer">Jenkins</a>.</p>
  
  <p>Now you would like to combine these two worlds (Vagrant and Jenkins) to get the perfect Continuous Integration Environment. To be more specific, you would like not to install the SW required by your project on the machine running Jenkins, but you would like to use the virtual environment provided by Vagrant to periodically build your project on the top of it. The CI software (Jenkins) will build the Vagrant box for you and build and test your project on the top of it.</p>
  
  <p>How would you setup your environment to achieve this?</p>