Jenkins is a robust, multi-platform continuous integration server that can help standardize the way code inspection and integration testing is performed. As we move forward in an increasingly Agile world, code that is portable, verifiably sound and deployable with repeatable procedures is in high demand. At the same time we are seeing more and more distributions; projects which combine contrib and custom code which cater to specific use cases. Drupal is rising to compete both in developer friendliness and to meet more sophisticated organizational needs out of the box. Organizing projects with make files, and performing frequent and comprehensive testing of builds from these project make files is important to ensure integrity not just of modules, but of whole products.
While Jenkins can’t give you all of this out of the box, a little free help from Drupal consultancy agency Reload and Aegir guru mig5 can get you there. This presentation will start with a brief overview of how some modern web application frameworks enforce healthy development practices, and how we can apply these practices to Drupal. Next, we will give a detailed overview of setting up Jenkins (especially for small and medium-sized environments). After Jenkins installation, we will share our resources on how to configure periodic or triggered Drupal builds with automated testing, code analysis and notifications. Along the way, you will hear about some tools that have transformed our approach to local development (lots of drush magic!).
At the end, participants should be able to get up and running with Jenkins in their own environments, and be able to make a strong case for introducing continuous integration into their organizations.