Continuous integration (CI) is a practice in software development that builds, tests and deploys changes automatically, usually multiple times a day, on each change to a code base. Find out how this practice can apply specifically to Drupal projects and see a working continuous integration setup in action and in a Drupal context.
The presentation defines the different build, test and deploy stages of a CI workflow and gives tool recommendations for each stage including Drupal specific demonstrations.
Continuous integration
It's important to have clean seperation between building, testing and deploying changes as they flow through your pipeline so that you can use the best tool for each stage. Whilst traditionally the domain of compiled language projects, we will cover what a build means in the context of a PHP/Drupal project, how and when to run automated tests and finally automated deploys to different environments (and rolling back when things go awry).
Build
Automated builds form the core of any CI setup. Our first look at tools will be at phing to perform builds in any environment in a way that can be triggered automatically.
Test
The ability to run automated tests and collect and respond to the results.
Deploy
We will cover options for automating deployments across different environments.
