MariaDB Buildbot, the journey of a reinvention
summary
MariaDB rebuilds CI with Buildbot using a multi-master UI/master split and Docker latent workers that spawn containers per build. The system defines ~50 OS images and ~100 test configurations, creates source tarballs, bintars and packages, and runs ecosystem tests. Fixes include setting build_wait_timeout to avoid stale containers, forcing UTF-8 encoding to stop sporadic SIGPIPE kills of mysql-test-run, moving large artifacts over SSHFS to avoid Buildbot data API slowdowns, and limiting logs because Buildbot saturates at about 10k lines/second.
AI-written summary · about
chapters (6)
- 0:00Introduction to MariaDB Buildbot
- 1:50Multi-master setup and architecture
- 4:06Docker latent workers approach
- 8:16Buildbot workflow steps
- 10:07Key challenges and solutions
- 16:31Q&A and closing remarks
related talks
37mDelivery and Debugging MariaDB Docker Official Images
24mFrom Zero to a Full Docker Based IT Teams
32mUsing Docker in test automation
28mMariaDB Database per user, on demand (aka systemd multi-instance socket activated)
50mComposing your Containerized Microservices
44mConfessions of a DBA: worst and best things I've done in production
28mWhat's New in Docker Build
31mDude, Where's My Build? Android CI/CD