CI/CD BoF: Delivering Quality Quickly
summary
Room debates concrete CI/CD tradeoffs: teams report replacing Jenkins with GitLab CI for YAML-as-code simplicity, others run self‑hosted Drone at ~200 repos and plan to scale workers from 10 to 20, Jenkins X appears quick but lacks HA, and Netflix-style automated canary analysis (Kayenta) is recommended over naive percent splits. Zalando describes a multi‑year effort that moved from huge Jenkins queues (5,000 backlog) to >100 Jenkins instances and a custom CI for compliance and secret handling.
AI-written summary · about
chapters (7)
- 0:00BoF introduction
- 1:04Ground rules
- 12:11Voting topics
- 17:42Canary releases
- 24:08CI/CD tools
- 35:09Custom CI/CD
- 36:11Closing remarks
related talks
35mJenkins Scaling and Organization for an Efficient CI
48mDemystifying CI/CD
23mMoving from Jenkins to Jenkins X: Scaling and Accelerating CI/CD
24mCI/CD Best Practices to Deliver Software Faster
05mCI/CD doesn't necessarily mean Jenkins
46mGitOps, Jenkins X & the Future of CI/CD
47mGitOps, Jenkins X & the Future of CI/CD
39mRemove your Testing Bottleneck with CI/CD Pipelines
