Gradle + CI vs. Modulezilla: Winning the War
summary
Capital One describes a custom system that layers modules.json on Gradle plus Fastlane and Jenkins to treat select libraries as source or binary, produce Maven artifacts to Artifactory, and enforce a single source of truth. The repo grows to 100+ modules and a full clean build plus unit tests runs ~3 hour clean build. Automation adds multi-merge to batch PRs, increase merge throughput, and tag/version artifacts; it works but still needs better test parallelization, feedback, and sharding.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:31Who are we?
- 1:06What are we here for
- 1:29What we are not here
- 2:25What Problems?
- 2:56Our Toolbelt
- 3:47(Typical) Project Struc
- 9:29defaults.json
- 16:47Fast-wat?
- 17:17How We Use Fastlane
- 19:28Modules.json && Fast
- 24:34Suggestions
related talks
41mBreaking the build
40mNail your Gradle build time
44mGradle: The Build System That Loves To Hate You
01h 03mPower of Gradle
02h 49mGradle: Give Your Build Some Love and It Will Love You Back!
35mGradle recipes for reducing your build times
43mBetter, Faster, and Stronger CI/CD Pipeline
52mFrom Laptop Builds to Advanced CI