Continuously delivering PHP projects
summary
Redesign of Time Out uses a Continuous Delivery pipeline that produces a single artifact is a zip named by commit hash built with phing/composer, tested with PHPUnit and Behat, and stored on AWS S3. Jenkins triggers builds from GitHub, Ansible provisions servers and ansible deploys from S3 to QA/staging, generates environment parameters.ini per environment, runs automated sanity checks, and leaves production deploy as a manual button. Expect ~3 minute builds, ~30s deploys, ~5+ minute tests, automated roll‑forward/rollback and strong org-wide buy‑in.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:17TOOLS OF THE TRADE
- 8:21A ANSIBLE
- 11:06BUILDING THE PIPELINE
- 23:15Split into two jobs in Jenkins 1. Run deployment script (production) 2. Run automated tests against production
- 33:26ROLLING BACK
- 34:14AUTOMATION
- 34:56YOU'LL NEED ALLIES
related talks
01h 01mA team's transition to Continuous Delivery
41mContinuous Delivery of a webapp by example
35mPractical PHP Deployment with Jenkins
33mSimplified Continuous Integration with Laravel and Jenkins
45mHighway to Continuous Integration
38mWhat's Really to Blame?
40mThe Butler Did It: Putting Jenkins To Work For You
46mJuggling features to production: Continuous Delivery in PHP