The Butler and the Snake - Continuous Integration for Python
summary
An existing Buildbot setup gets replaced by Jenkins with GitHub post-commit hooks to enforce one build per commit, because nightly batches leave the tree broken 99% of the time. The CI runs ~9,000 tests across ~300 packages (full test suite ~1.5 hours, typical CI build ~40 minutes), uses Robot Framework + Selenium (with Sauce Labs), pytest XML, coverage/Cobertura, and plone.recipe.codeanalysis feeding Jenkins plugins. The pipeline yields a green build most of the time and lets releases proceed without days of manual test-fixes.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:48What is Continuous Integration
- 2:30BuiltPot
- 3:23Jenkins
- 5:00nightly builds
- 9:02Automated build
- 10:09Testing
- 11:15Acceptance Tests
- 13:03Static Code Analysis
- 14:00Notifications
- 15:26Builds
- 17:34Agreement
- 18:06Keep a green build
- 20:33Scalability
- 21:13Continuous Delivery
- 22:32Summary
- 23:12Recommended books
- 23:31Blog post
- 23:56Questions
related talks
30mThe Butler and the Snake: Continuous Integration for Python
40mThe Butler Did It: Putting Jenkins To Work For You
27mAutomation, Innovation and Continuous Delivery
29mFrom scheduled builds to commit triggered pipelines
45mHighway to Continuous Integration
35mMassively Continuous Integration: From 3 days to 30 minutes
01h 12mPitfalls of Continuous Deployment
28mBest Practices for Continuous Integration in Python V02