Dailymotion's Continuous Delivery Story
summary
Dailymotion migrates CI/CD to Jenkins X + Tekton on Kubernetes, implements GitOps workflows, and gives each pull request a preview environment per PR. The pipeline enforces automated unit/integration tests and declarative configs so teams test and validate before release, moving from big‑bang releases to a two‑week cadence of small, independently deployable changes. Results: far fewer manual steps, faster rollback and progressive releases, and teams owning delivery end‑to‑end.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:57What are the issues?
- 2:19What can be done?
- 3:46How to do it? Jenkins X + Kubernetes
- 4:24Why Jenkins X?
- 6:02Practices first
- 7:27Jenkins X practices (incl. GitOps)
- 9:44Benefits
- 13:01Preview environment benefits
- 15:38Results
- 16:57New challenges
- 17:49Conclusion
- 19:15Q&A
related talks
24mContinuous Delivery
39mJenkins X Progressive Delivery For Kubernetes
50mKubernetes First Continuous Delivery for Developers
36mCI/CD BoF: Delivering Quality Quickly
01h 01mA team's transition to Continuous Delivery
46mGitOps, Jenkins X & the Future of CI/CD
01h 20mTuesday Keynote
29mContinuous Integration and Continuous Delivery Pipelines: Just the Basics