Monorepo - One Repo To Rule Them All
summary
Company consolidates ~dozens of repos into a single monorepo using the to-mono script (modified to handle non-master branch names) and preserves history by moving each repo into its own subdirectory. CI uses GitLab CI generate job that git-diffs branch vs remote, expands changed services via a YAML dependency map, then dynamically emits per-project jobs. Python specifics: Pipfile/Pipfile.lock, editable installs instead of PyPI pushes, per-service virtualenvs. Result: single merge request runs all relevant tests and simplifies dependency alignment and deployments.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:15The Monorepo Decision
- 2:15Root Causes and Challenges
- 6:50Benefits of Monorepos
- 8:45Structure Comparison
- 11:05Python Best Practices
- 13:30Implementation Roadmap
- 18:27Q&A and Conclusion
related talks
30mForget Mono vs. Multi-Repo: Building Centralized Git Workflows for All Apps
36mA fresh take on monorepos in Python
21mTeach Your Old Code New Tricks: Automating Code Quality in Large Projects
07mLightning Talk – Python Dependencies the Right Way
41mDemystifying West
26mCLI, CI, DIY: Crafting Python Based Dev Tools in a DevOps Vacuum
39mMoving to pyproject and tox
27mRelease Management with Devpi