Continuous Integration and Deployment with PHP

You've no doubt heard the terms before. This short presentation goes over why you should consider Continuous Integration/Deployment and how it can make your life as a developer easier and more productive.

Transcript

1. Continuous Integration and Deployment with PHP Samantha Quiñones - DCPHP Meetup - June 11, 2013
2. About Me Samantha Quiñones http://about.me/samantha.quinones samantha@tembies.com @ieatkillerbees
3. My Awesome Job (HELP WANTED!)
4. What is CI/CD? • Frequent builds • Automated build/test/release • Hands-off deployment
5. But first...
6. T ypical Build Process • Update config files • Create SQL scripts to update the DB • Run tests
7. T ypical Deployment Process • (S)FTP • git pull / svn update • rsync
8. T ypical Deployment Process • (S)FTP • git pull / svn update • rsync
9. T ypical Deployment Process
10. Building & Pushing by Hand Sucks • Error prone • Encourages dirty hacks • Time-consuming • Integration Hell
11. Building & Pushing by Hand Sucks
12. You might have a deployment problem if... • “I don't know, it worked on my machine.” • “Who deployed X? X wasn't ready for prod!” • “Well, in production, you have to...” • PackageRepository_20130313.php
13. Continuous Integration (one better way) • Practice of Extreme/Agile Programming • Martin Fowler & Kent Beck
14. What's the Point? • Build one thing & integrate it immediately • When an enhancement is made, software is ready to ship • Building is automated and repeatable
15. Getting Started • Automated Tests • Testable Code • Production-like environment
16. Getting Started • Automate your build (Ant, phing, make, rake, etc) • Let your tools handle your config changes <property name="env" value="default" /> <property file="build/properties/build.properties.${env}" />
17. Config File: "logging": {"logfile": "@@logpath@@"}, "database": {"dsn": "@@datapath@@"} Properties File: app.logpath = ${paths.var}/logs app.datapath = ${paths.var}/data
18. Automate Database Changes • If you use an RDBMS and don't use a migration tool, start! • Many major frameworks • Liquibase, dbdeploy, alembic (it's not just for python!)
19. What Does a Good Build Look Like? • Tests Pass • Code Coverage • Coding Standards • Static Analysis • Documentation
20. Choose Your Weapon
21. Discover Problems Quickly
22. Build History and Data
23. Enforce Use of QA Tools
24. ABCs of Continuous Deployment A lways B e s C ipping (Anglo-Saxons need love too!)
25. Deployment is Tricky • Deploy Test Commit or Rollback → → • Versioned directories & symlinks
26. It's 3 am. Do you know where your hackers are? • When deployments fail, back them out! • Fixing code in production is a terrible idea • Missing a deadline sucks. Releasing crappy code sucks more.
27. Don't Be a Cowboy
28. The Beating Agile Heart User story Enhancement Release → → • Testable, reproducible results • Be confident in your product • Give end-users a window in to dev cycle
29. Next Steps? • “Continuous Integration” by Martin Fowler http://bit.ly/KEgGa • Chris Hartjes' Grumpy Learning http://bit.ly/11fxCcY • Marcelo Gornstein's Blog http://bit.ly/192nVCw • Email or tweet me!
30. Questions?