1. Site Deployment Module
Continuous Integration w/ Drupal
Philippe Labat
12 Septembre 2015

2. Agenda Introduction to Continuous Integration
Overview of a Simple CI Workflow
What is a site deployment module
Demo time!
Conclusion
Q & A

3. Once upon a time…

4. What is Continuous Integration?

5. The goal is to automatically run your entire deployment workflow on every commit to make sure all the features are still working.

6. Minimize the duration and effort required by each integration episode
Be able to deliver at any moment a
product version suitable for release

7. Overview of a simple CI Workflow

8. Best Practices
All, all, ALL your configurations should into code.
Noooooooo Database cloning!
Use version control! (Git, … Git, or Git)
Create automated tests! (Functional or Unit)
Include your environment setup in your code and get rid of your sysadmin! (Vagrant + Ansible or Docker)

10. Site Deployment Module

11. What does it do?
Automate the provisioning of your entire website including configurations, modules, themes, taxonomy, menus & even some content using only 1 command.
During development, it lets you deploy new features incrementally. ( using hook_update_N() )

12. How’s that even possible?
Features to import various type of configuration such has: Content Types, Menus, Views, etc… [+ Contrib]
Strongarm is used to export/import variables using Features
Context is used to handle page layout, block dispositions, etc…

13. drush en sdm -y

14. Demo Time!!!

15. Conclusion
Take back control over your deployment
Stop sending broken code to your QA Team
Let your client win and deploy every 15 minutes for the rest of their lives.
In Drupal 8, you will simply need to replace Features with the core config manager.

16. Questions?

17. Albert Albala (http://dcycleproject.org)
1. Entreprise
Ressources
Albert Albala (
Martin Fowler (
Example of a Site Deployment Module (

18. Thank You