From Fix to Final Release: Continuous Integration and Testing for Diego
summary
Diego’s CI pipeline runs an automated left-to-right Concourse flow that compiles releases, deploys to a locked ketchup acceptance environment, runs unit, component, ego (cross-component) tests, CF CATS acceptance suites, a 1.5 hour upgradability suite that verifies piecewise upgrades from older releases, and post-delivery BBS benchmarking. The pipeline has about 51 jobs across six-plus BOSH environments, marks candidate builds as delivered, requires a manual PM approval to ship, and catches manifest, routing and upgrade regressions before release.
AI-written summary · about
chapters (19)
- 0:00Start
- 0:15Diego Team
- 1:15What this talk is about
- 2:06What this talk is not about
- 5:36Test Driven Development
- 6:24Local Dev & Test Cycle
- 11:31Create BOSH Releases
- 12:27Wait for Bosh
- 13:16Deploy
- 14:15Smoke Tests
- 14:38Acceptance Tests
- 16:40DUSTS
- 19:00Deliver
- 20:03Github Release
- 20:24Merge to Develop
- 20:37Vizzini
- 21:56Benchmarks
- 22:48How much is too much
- 23:55Conclusions
related talks
01h 01mA team's transition to Continuous Delivery
30mOur Continuous Delivery Journey
29mConcourse in the Real World: A Case Study in CI/CD and DevOps - Greg Meyer & Bryan Kelly, Cerner
40mCode, Test, Deploy, Repeat
32mClimbing the Mountain of CI/CD: A Tester’s Tale
01h 00mDeep Dive: Self-driving Pipelines: Building the Unbreakable Continuous...
01h 12mPitfalls of Continuous Deployment
28mClimbing the Mountain of CI/CD: A Tester’s Tale