LinuxCon + CloudOpen + ELC-E Europe 2014

Jenkins is often found inside a Continuous Integration/Delivery infrastructure. It can be used to automatically test each change set as soon as it occurs in a monitored code base. It is often linked with deployment tools like Vagrant to create a complete testing environment. Yet, here is a small drawback: launching and provisioning virtual machines for each change set increases the time for a test run to complete. With the help of Docker, provisioning of a testing environment is done in seconds, decreasing the time it takes to provide meaningful feedback to the developer. This talk describes two scenarios where automatic integration testing with Docker increases the productivity of admins and developers. The first one describes how an admin may perform integration testing of Puppet modules, a second one implements integration testing of a web app consisting of a Web and database server.