Improving developer productivity with Gradle Enterprise in 2023
summary
Gradle Enterprise shows where builds waste real time and how fixes actually behave: a 60s waste across 50 builds by 50 developers equals ~42 hours lost per day, so build scans plus the task inputs comparison pinpoint cache misses such as live literals writing absolute paths and a KSP subplugin option that needed an internal fix, configuration-cache misses debugged by attaching a debugger to Gradle, artifact transforms now visible in scans, and a beta test API that detects flakiness, drives CI automations (run a new UI test 10× and block PRs) and feeds dashboards.
AI-written summary · about
chapters (18)
- 0:00Introduction and speakers
- 1:06Speakers background and roles
- 3:11Slow builds as technical debt
- 4:37Build scans and Gradle Enterprise overview
- 5:43What is build caching
- 7:51Debugging cache misses with build scans
- 8:11Common cache misses and fixes
- 10:38Debugging cache misses in KSP
- 14:33Configuration cache misses
- 17:27Beyond caching with Gradle Enterprise
- 18:29Flaky tests problem and solutions
- 19:55Gradle Enterprise Test API introduction
- 23:25Preventing flaky tests in pull requests
- 25:10Flakiness reports and dashboards
- 28:03Repository correlation with tests
- 30:50Integrating Gradle Enterprise with CI
- 32:37Artifact transforms in build scans
- 36:55Q&A and closing remarks
related talks
33mKeeping your Gradle builds in top shape
36mImproving Gradle Builds
19mAvoiding work is work - but it pays off!
36mKeeping your team’s Gradle builds in top shape
37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
27mDeveloper Experience: It’s Time to Start Complaining
30mAndroid Developer Productivity
41mKeeping your team's Gradle builds in top shape