Continuous Integration
summary
Continuous integration is practical for tiny projects when specific pieces are chosen: enforce a coding standard and run PHP_CodeSniffer, add small unit tests with PHPUnit and SimpleTest (or Selenium for browser checks), automate builds with Phing or Maven and run the pipeline on Jenkins or TeamCity. Multiple integrations per day, automated tests, and automated DB backups turn manual whiteboard steps into repeatable scripts. Examples: a two‑month one‑file job needs only standards and a few tests; monthly surveys need build automation; large apps need everything plus Sonar technical‑debt reporting.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:46Audience Participation?
- 2:34Step 1
- 3:47Measuring Code Quality
- 4:35PEAR Coding Standard
- 5:26Custom Standards
- 6:19Output
- 7:50Unit Tests
- 8:45Tips
- 9:58How Many Tests?
- 10:44Testing Frameworks
- 11:59Simple Test
- 12:09Selenium
- 13:16Automate The Build
- 15:42Documentation
- 18:05Continuous Integration Tools
- 19:42Hudson and Jenkins
- 20:48Reporting
- 22:40Technical Debt Plugin
- 23:32A Little Help
- 25:42Quick Recap
- 30:47Take Away #1
- 31:12Take Away #2
related talks
31mContinuous Integration 101 for Devs
46mContinuous integration - that's not what they meant
34mContinuous Integration: A Bittersweet Love Story
45mContinuous Integration: That’s Not What They Meant
01h 15mThe Practices That Make Continuous Integration
32mBuilding Confidence Together: Continuous Integration & Testing
01h 00mAutomation Engineer’s Way to Continuous Integration
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers