From scheduled builds to commit triggered pipelines
summary
They move a legacy schedule-based CI into Jenkins pipelines as code, switch from Subversion to Git with branch builds and pull‑request gates, and break the monolith into component pipelines so a web UI build completes in about five minutes. The codebase runs 70,000 unit and 130,000 integration tests per week, they provision agents dynamically, publish semantically versioned artifacts, and report faster commit feedback and a greener mainline with independently tested build artifacts.
AI-written summary · about
chapters (29)
- 0:00Intro
- 1:20The holy grail
- 1:58How many bills
- 2:38How many tests
- 3:07Continuous integration
- 3:59MapController
- 5:15Rebuild everything
- 5:36Fragile
- 5:52Sand
- 6:09Ants
- 6:37Lifecycle of a commit
- 7:41Integration test
- 8:34Integration time
- 9:04Building in parallel
- 9:33Virtual machines
- 10:14Branches
- 11:20Break the bills
- 12:40subversion
- 13:02git forget
- 14:55workflow
- 15:57gatekeeper
- 17:46Jenkins Free
- 19:58Web UI
- 20:59Component
- 21:45mama loop
- 22:31components
- 23:37pipeline screenshots
- 25:44Challenges
- 27:15Next steps
related talks
30mImplementing Continuous Deployment with Jenkins & Gerritt
13mEvolution of containers in continuous integration
34mContinuous Delivery with Jenkins Workflow
27mAutomation, Innovation and Continuous Delivery
27mConcept to Code to Runtime - Simplify, Enable, Exploit
39mRemove your Testing Bottleneck with CI/CD Pipelines
01h 01mA team's transition to Continuous Delivery
46mThe Software Factory