Speeding up Jenkins, Gradle, and Maven with a Build Cache
summary
Claim: enabling Gradle or Maven build cache cuts clean build+test time dramatically — demos show a Gradle project dropping from ~4s to sub‑second by pulling three tasks from cache, and a remote cache node (Docker) serves entries to local builds and CI. Implementation details: set org.gradle.caching=true, run a remote build-cache server, integrate with Jenkins or any ephemeral CI. Real numbers include a Netflix case of 62 min → <5 min, a config flag org.gradle.caching=true, and a remote cache node (Docker).
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 10:19What is build caching
- 16:21Local caching demo
- 24:36Multi-module caching benefits
- 28:11Remote caching with CI
- 34:46Remote caching demo
- 38:46Q&A and resources
related talks
40mNail your Gradle build time
19mGetting to a green build with caching on CI
01h 39mWorkshop: Maximize Developer Productivity with Fast and Reliable Gradle and Maven Builds
23mWalk, Run, Fly - Take your build pipeline to the next level!
49mAccelerating Maven Builds: From Snail's Pace to Rocket Speed
54mDeveloper Productivity Engineering Deep Dive
54mFrom Laptop Builds to Advanced CI
30mHow we brought down our build times. General optimization tips