Developer Productivity Engineering for Open-Source Communities
summary
Gradle’s Develocity platform promises concrete gains: captures build scans (full runtime metadata) so CI vs local diffs and flaky-test histories are immediately visible, applies build caching, predictive test selection and test distribution across agents, and reports measured wins — Spring saves ~19 days of task time, a project saves 27 days via predictive selection, and a build drops from 47 to 11 minutes with distribution plus caching. Works with Maven/Gradle/Bazel, local or CI, and is already used by JUnit, Spring, Quarkus, Apache and Micronaut.
AI-written summary · about
chapters (14)
- 0:00Developer Productivity Engineering
- 1:11Developer flow and tooling
- 3:18Inefficient tool chains disrupt productivity
- 7:50Developer Productivity Engineering discipline
- 9:35Velocity for build insights
- 12:03Build data and build scans
- 17:21Analyzing flaky tests
- 20:29Faster feedback cycles
- 22:17Build caching
- 25:49Predictive test selection
- 27:36Test distribution
- 29:01Real-world impact
- 34:12Easier open-source contributions
- 38:47Velocity in open-source
related talks
36mDeveloper Productivity Engineering: What's in it for me?
44mDeveloper Productivity Engineering: What's in it for Java Developers?
37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
54mDeveloper Productivity Engineering Deep Dive
43mDeveloper Productivity Engineering – The Next Big Thing in SW Development
27mDeveloper Experience: It’s Time to Start Complaining
19mAvoiding work is work - but it pays off!
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development