Rootconf 2012

Build a workflow where your Drupal development team can just commit their code to GIT and automatically deploy changes across development, testing and live environments.

Outline

This talk will familiarise you with the process of pushing your Drupal site’s configuration that’s typically stored in a database to code using Features [1] and then taking a change from a local dev environment to test, stage, and live, all by Jenkins CI [2] discovering changes to a GIT repository and rolling out instructions to each environment to generate a new build.

We use Drush make [3] and Aegir [4] to manage and host different platform builds and Fabric[5] to issue commands on remote servers with SSH.

[1] http://drupal.org/project/features

[2] http://jenkins-ci.org/

[3] http://drupal.org/project/drush

[4] http://aegirproject.org

[5] http://docs.fabfile.org/en/1.4.1/index.html

Speaker bio

Kaustubh Srikanth is a technologist based in Bangalore, India. Nowadays, he spends a lot of time managing other people’s Drupal code across different environments and servers.