iOS Monorepo CI/CD Pipelines
Article Summary
Alberto De Bortoli from Just Eat Takeaway reveals how they slashed their iOS CI complexity by consolidating dozens of module repos into one. The result? One PR instead of multiple, faster iteration, and smarter pipelines.
Just Eat Takeaway's iOS team faced a painful workflow: every module change required multiple PRs and independent versioning across separate repositories. They migrated to a monorepo using CocoaPods development pods and built dynamic Jenkins pipelines that intelligently detect which modules changed and run only the necessary tests.
Key Takeaways
- Monorepo reduced module changes from 2+ PRs to just 1 PR
- Dynamic pipelines detect changed modules and run targeted tests automatically
- Smart dependency tracking runs tests for consuming modules when dependencies change
- Agent pool reduced from 10 to 5 nodes through aggressive optimization
- Custom version pinning rules balance stability with update flexibility
Just Eat Takeaway's monorepo approach eliminated multi-repo overhead while maintaining modular architecture benefits through intelligent CI pipelines that scale automatically as new modules are added.
