Workshop: Maximize Developer Productivity with Fast and Reliable Gradle and Maven Builds
summary
Hands-on workshop shows how to use build scans and remote build cache to measure and fix Gradle/Maven bottlenecks: capture every local and CI build, run a profiler, compare two builds on the same commit, and spot cache misses or absolute-path inputs. Examples include an 80% faster build after caching, an 81% cache-hit case, CI savings of ~15 minutes per build, and teams (six devs) running ~16,000 builds in three months — practical labs produce reproducible scans and fixes.
AI-written summary · about
chapters (10)
- 0:00Introduction to DevPro engineering
- 10:02What is a build scan?
- 23:17Extending build scans with metadata
- 38:27Build comparisons for debugging
- 48:02Impact of fast builds on productivity
- 55:30Local build cache setup
- 1:06:13Cachability tests and optimizations
- 1:15:03Remote build cache benefits
- 1:26:19Why Gradle Enterprise matters
- 1:35:29Q&A and closing remarks
related talks
41mSpeeding up Jenkins, Gradle, and Maven with a Build Cache
36mImproving Gradle Builds
54mDeveloper Productivity Engineering Deep Dive
40mNail your Gradle build time
33mKeeping your Gradle builds in top shape
36mKeeping your team’s Gradle builds in top shape
20mMaximize development efficiency with expert CI/CD strategies
43mThe Secrets of the Build Scan Plugin and the internals of Gradle