It's Not Called Continuous Integration (CI) for Nothing
summary
SOASTA builds a Jenkins-driven conveyor belt that automates change → configuration → release so the company ships fast and measures regressions against baselines. Concrete claims: ~22 major builds a day, ~454 builds last year, 8,000 tests/day and 300 mobile functional tests; real user data feeds test cases. The talk shows Jenkins pipelines, cloud device pools (NTT), and a working feedback loop that enabled over 100 product releases in 2014 — Big 3 processes and baseline comparison.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:20Agenda
- 2:14Booth
- 3:00Need for Continuous Integration
- 3:40Continuous Feedback Loop
- 4:44The Big Three
- 5:42DevOps
- 7:02Silos
- 7:32The Big 3
- 8:57Software
- 9:35Why Continuous Integration
- 11:06The Conveyor Belt
- 11:58The OSI Model
- 15:00Architecture Map
- 15:23Factory
- 18:12Change Management
- 18:51Testing
- 21:42Baseline
- 23:30User Experience
- 24:18CloudTest Example
- 25:47Regression Tests
- 26:07Release Candidates
- 27:08Summary
- 31:40Final Takeaway
- 32:28Trivia
- 34:00Questions
related talks
27mAutomation, Innovation and Continuous Delivery
35mMassively Continuous Integration: From 3 days to 30 minutes
34mUsing Test Automation for Continuous Integration, Delivery and Quality
45mHighway to Continuous Integration
42mAutomation, Innovation and Continuous Delivery
29mFrom scheduled builds to commit triggered pipelines
32mBuilding Confidence Together: Continuous Integration & Testing
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins