Docker powered concurrent automated testing

Operations people want stability. Developers want change. How can you allow for needed changes while maintaining stability? How can developers know that their code will work in production? Will your testing platform support a dev team submitting several merge requests?

This session will demonstrate how Docker can be used to unify the team's environment and be consistent with the testing server and production. Learn how to bake your infrastructure as code into your project git repo. Align automated tests and sandbox environments with your production architecture. Running tests only on the main development branch can lead to broken builds, while forcing developers to run full test suites locally before pushing damages productivity (especially on non-trivial sites with hundreds of tests). We will demonstrate a process to trigger tests on each pull request and run them concurrently, providing consistent, repeatable builds and ensuring that broken code is never, ever merged.

We have experienced a variety of pain points using Docker for Drupal development. Come and see how we are using the open source Bowline Drupal development tools project to overcome these difficulties and have a smooth Docker experience for developers, even on OSX. Learn how to use Bowline to configure and build docker containers, use drush commands within the container, and run Behat tests on a Jenkins server.