Development workflow with CI, github and vagrant

DrupalCamp Berlin, November 2014

About me• Yuriy Gerasimov• Developer & Drupal Architect• @ygerasimov

Problems● different people on the team jumps in & out● quality of the project● master database

People jumps in● fast environment setup is critical● same environment● same tools (adminer, drush aliases, ssh keys)

Vagrant● VirtualBox (other providers avaialble)● text file config● provisioners (puppet, chef, shell)● starting point puphpet.com, phansible.com

Quality● code review● code style checks● automated tests

Code review● comment code on pull request● test build site

Jenkins● code style checks (code sniffer, jshint, css-lint)● run tests● build site● other jobs (clear caches)

Profile● site as installation profile● demo content (partial import, custom code)

Code structure● all code in one repo● branch per environemt

Future• docker• behat

Dev process

Production• peaks• late client testing• sync dev & theme• people planning

Prototypes• clickable set of pages• frontend technologies

Prototypes dev• panels + panelizer• custom panes• view modes

Team

Team• architect (solutions, estimates)• PM (communication, budgets)• developers (implementation)• front end (prototype)• qa (testing)

Questions?