DrupalCon Los Angeles - Continuous Integration Toolbox
4 likes4,324 views
This document describes a multidimensional continuous integration (CI) workflow for Drupal projects using tools like Vagrant, Ansible, Jenkins, and other automation tools. It provides an overview of how code is developed locally, reviewed through pull requests, tested through automated jobs, and deployed across environments like development, staging, and production. The goal is to standardize and streamline the development process, improve quality, and reduce bottlenecks through automation. Key aspects covered include local development environments, database/configuration handling, code review process, automated testing, and deployment.
DrupalCon Los Angeles - Continuous Integration Toolbox
- 2. https://github.com/propeoplemd/cibox Multidimensional testing workflow before merge to master @ygerasimov @podarok
- 3. Introduction Yuriy Gerasimov Drupal Architect https://www.drupal.org/u/ygerasimov Andrii Podanenko DevOps Architect https://www.drupal.org/u/podarok
- 4. Development infrastructure ● single development environment ● separate company dev server (multiple vhosts one per project) ● SaaS solutions (Acquia, Pantheon, …)
- 5. Coding process ● all commits directly to master ● master deployed to dev site (sometimes automatically) ● code review on dev site after deployment
- 6. Configuration process ● master database, get pulled to local dev environments (backup & migrate) ● changes to configuration happens on dev site manually
- 7. Problems ● shared resources on dev environment, dev conflicts (cache, solr) ● too much time to configure all services locally (varnish, solr) ● large distance between Dev and Ops (only one guru able to do production release)
- 8. Local development ● local virtualized environment (vagrant) ● started from puphpet.com but switched to ansible ● based on ubuntu 12.04 (upgrading to 14.04)
- 9. Database ● no configuration on demo/stage/prod sites ● code driven development ● database/profile workflow
- 10. Code process ● Github pull requests workflow ● code review before merge to master ● code style checks, test runs ● security tests ● QA on builds
- 11. Extra tools ● os monitoring to see resources consuming operations (multinode munin) ● visual regression testing ● automated complex deployments Acquia deployment ● urls health checks
- 12. Visual regression ● http://backtrac.io SaaS ● screenshots before / after release, diff ● automated scheduled screenshots / diffs ● authenticated user ● register and start using now!
- 14. URLs health checks ● https://github.com/ygerasimov/website-size-scan ● scans all URLs in the file, checks sizes of images ● logs 404s, 5xx, etc.
- 16. CI for project and VM with Drupal initial codebase Project initial creation playbook ( github.yml ). - Get latest Drupal - Install basic profile - Inject Vagrant VM config - Inject DevOps scripts - reinstall.yml, - sniffers.yml, - tests.yml, - security.yml Continuous Integration for a project ( jenkinsbox.yml ) - Server preconfigured packages, swap, needed stuff - Jenkins, sniffers, ansible - Jenkins preconfigured jobs - Apache, mysql, solr etc - Optimized configs, vhosts etc CIBox code structure
- 17. Steps for getting started 2. Repository initialization ● Make needed changes to github.yml ● Run ansible-playbook github.yml ● push generated codebase folder to github repo ● check Pull Request builder with newly created change to readme.md ● profit 1. CI server ● Get virtual or real server from hosting provider (Ubuntu LTS 64 bit only for now) ● Set root password ● Make initial config changes to jenkinsbox.yml and inventory ● Run ansible-playbook jenkinsbox.yml from a shell ● Make changes to jenkins UI with credentials to github repo How to deploy whole system
- 18. ansible playbook for installing CI server - Jenkins powered install - Needed Jenkins’s plugins - LAMP stack + SSL - PHP Code Sniffer, scss-lint - Java JDK - Jetty && Apache Solr - Selenium && Behat packages - Optimized and preconfigured configs jenkinsbox.yml
- 19. A bunch of jobs with scripts for running playbooks Preconfigured Jenkins - Pull Request Builder - Skeleton for Backup production database - Demo site builder - Disk space cleaner
- 20. During run of github.yml you’ll get a codebase that has latest drupal in drupal folder and scripts for future CI builds and tests. Latest drupal, adminer, devops scripts, basic profile Main project code structure
- 21. Vagrant + virtualbox (optional lxc) + ansible provisioner We are using trick for sharing ansible roles between CI server and VM provisioning scripts for making sure we have equal environments for both. Basic stuff for now (all are inside splitted ansible roles): composer, pear, ansible, apache, memcached, mysql, php, sdebug, shprof, selenium, behat, drush, jetty solr, phpdaemon, php codesniffer, apache ssl, custom swap. Just vagrant up and you are ready to go coding. Vagrant box
- 22. Single task flow Developer point of view
- 23. Comments by CI bot
- 24. Profile based flow Reinstall Drupal from scratch every builder time
- 25. SQL based flow Import SQL dump every build and prepare it to codebase
- 26. Team rules ● Never merge own Pull Request ● Never push directly to main repo master branch ● master branch is stable ● There should be two siblings for every role (optional) ● Bugs introduced from specific PR would be nice to assign to its reviewer. (optional)
- 27. Development phases 1. Reinstall from scratch every build by reinstall.yml playbook 2. Update path, content can be edited at stage by reinstall. yml playbook and pp_environment: staging 3. SLA (production) update path with QA testing on stage
- 28. Responsibility Due to the fact all DevOps scripts are in the same repo with a project itself - any developer can change workflow at any point. Team does manage all the steps for DevOps scripts, no need to involve Ops into the team.
- 29. Flow Bottlenecks ● Dependency from github(gitlab, bitbucket) ● If CI server down - team get stopped on code review step ● New developers should follow new rules. (Coder is tough) ● DevOps must be a team member(s) ● Code Review get hurt ● Builds are slow on huge projects ● Decent desktops for a team (SSD is a must) ● Minimal task >=1 hour
- 30. Usefull links Documentation ● https://github.com/propeoplemd/cibox ● https://github.com/propeoplemd/cibox/blob/master/README.md ● https://github.com/propeoplemd/cibox/blob/master/github/files/drupal7/scripts/README.reinstall.md Presentations ● http://www.slideshare.net/podarok/drupal-continuous-integration-workflow ● http://www.slideshare.net/podarok/start-using-vagrant-now ● http://www.slideshare.net/podarok/live-deployment-ci-drupal ● http://www.slideshare.net/ygerasimov/ci-drupal-camp-berlin-2014 ● http://www.slideshare.net/ygerasimov/vagrant-stanford-drupalcamp-2014 ● http://www.slideshare.net/ygerasimov/continuous-integration-stanford-2014 Blog posts ● http://wearepropeople.com/blog/how-we-use-vagrant-in-our-drupal-development-workflow ● http://wearepropeople.com/blog/building-quality-into-drupal-development-workflow
- 31. Big thanks to Jeff Geerling @geerlingguy
- 33. WHAT DID YOU THINK? EVAULATE THIS SESSION - LOSANGELES2015.DRUPAL.ORG/SCHEDULE THANK YOU! Andriy Podanenko DevOps Architect Yuriy Gerasimov Drupal Architect