Gradle remote cache politics (and how we coach them)
Build performance is people — here is the worksheet we use to align platform and app teams.
Remote build caches fail when platform teams guard the keys and application teams distrust the hits. Our Gradle Enterprise Builds for Monoliths track introduces a shared worksheet: who owns eviction, what artifacts are too sensitive to cache, and how to prove hits with anonymized metrics.
We simulate a contested change where a security guild blocks caching for a signing task. Learners draft the compromise — ephemeral runners with scoped tokens — and attach it to their build scan narrative. The goal is an executive-ready story, not a vanity graph.
Week three adds a Bangkok-friendly office hour for teams that only overlap on Saturday mornings. We keep cohort sizes modest so mentors can read every spreadsheet row. Completion means a signed decision record, not a green pipeline alone.