Gradle Technologies

New from #Gradle! 🌐 #Develocity Universal Cache 🌐 Three revolutionary caching technologies in one place: 📦 Artifact Cache - Caching inputs before the build ⏱️ Setup Cache - Caching environments at build time 🔄 Build Cache - Caching outputs for future builds gradle.com/blog/universal…

Three Gradle talks at KotlinConf 2026, what's actually in each one: 1. A Tale of the Gradle DSLs (Paul Merlin) traces Groovy → Kotlin DSL → Declarative Gradle. 2. 10 Gradle Best Practices Every Kotlin Developer Should Know (Stefan Wolf) splits into organizing a build and optimizing it. 3. A First Look at the Kotlin Ecosystem Plugin for Declarative Gradle (Marcin Mycek) is a lightning talk on declaring your project's shape in .dcl files instead of scripting it. Recaps, takeaways, and links to all three talks: blog.gradle.org/gradle-at-kotl…

Three Gradle talks from KotlinConf 2026, recapped: 1. Paul Merlin on how we got from Groovy to Kotlin DSL to Declarative Gradle 2. Stefan Wolf on 10 best practices 3. Marcin Mycek on the Kotlin ecosystem plugin Which ones are worth your 15 minutes: blog.gradle.org/gradle-at-kotl…

Quick tip 🛠️ Build failing and you don't know why? #Develocity Build Scan shows you: - Exact failing task - Full console output - Dependency + config context - Comparison to past builds Stop scrolling CI logs. #Troubleshooting #CI

DuckDuckGo cut Android CI build times by up to 57%: - Diagnosed cache misses systematically - Fixed Room schema paths - Fixed Dagger non-determinism - Fixed CMake caching gaps 160 modules. Real fixes, not guesses. develocity.ai/blog/duckduckg… #Android #Develocity

New in #Develocity 2026.2! Build Caching Optimizer AI agents that autonomously: - Diagnose cache misses - Propose fixes - Learn from expert build knowledge Less guessing, more caching that works. develocity.ai/releases/2026.2 #buildcache #CI

We've been running Isolated Projects as our daily driver on the Gradle build itself. The results, measured over six months of real work in Develocity: median IDE sync roughly halved, from ~1m24s to ~47s. The slowest syncs (p95) fell from nearly 7 minutes to just over 3. How we migrated, what broke, and how we measured it: blog.gradle.org/isolated-proje…

Our KotlinConf talk is now on YouTube: A tale of the Gradle DSLs. Paul Merlin traces how Gradle's build languages got here -> from Groovy to Kotlin DSL -> and where Declarative Gradle takes the story next. 🎥 youtube.com/watch?v=k8T9IO…

Quick tip 🛠️ Diagnosing a flaky test in #Develocity: - Sort tests by flakiness rate - Flag anything above your threshold - Quarantine into a separate suite - Track pass rate until it's clean Stop guessing. Start measuring. #DPE #CI

@herudaio (aka Marcin Mycek)'s @KotlinConf talk is now on YouTube: A First Look at the Kotlin Ecosystem Plugin for Declarative Gradle. What declarative build configuration looks like for Kotlin projects and where the DSL work is headed. 🎥 youtu.be/25Ngfn9Bhqc

Gradle Technologies is now Develocity. The Gradle Build Tool is not renamed, not acquired, and not relicensed. It remains free, open source, and Apache 2.0 at gradle.org. What changed, what didn't, and why: blog.gradle.org/the-company-fo…

📣 Gradle 9.7.0 RC1 is out and ready for testing 🔬 docs.gradle.org/9.7.0-rc-1/rel… Bug fixes and… 🌱 Isolated Projects graduates to incubating ⚡ Broader Configuration Cache compatibility 🔍 More source locations in problem reports Please report any 🐛 on GitHub!

Every issue and PR on gradle/gradle now gets a human answer within a week. New on the blog: how we got there after retiring the stale bot, what our triage automation actually does, and how you can help us help you. blog.gradle.org/triaging-gradl…

Software shipped at human speed. AI just ended that. Gradle Technologies is now Develocity: same team, same access, sharper focus on governance and efficiency for AI-driven delivery. What changed and what stays the same: develocity.ai/blog/gradle-te… #Develocity #AI

That's a wrap on our Gradle-on-ephemeral-CI series. Part 3 takes on the execution phase and the Build Cache: reuse finished task outputs instead of rebuilding them on every run. blog.gradle.org/gradle-on-ephe…

Your CI re-downloads the same dependencies on every ephemeral build. Cache them once and Gradle's configuration phase drops ~28%. Part 2 of our blog series: blog.gradle.org/gradle-on-ephe…

Ephemeral CI wipes Gradle's caches on every build, so you pay the startup cost every run. We measured what actually fixes it: primed image ~24%, cached wrapper distribution ~22%, local mirror ~18%. Part 1 of 3: blog.gradle.org/gradle-on-ephe…

Running your full test suite on every PR is a choice — not a requirement. #Develocity Predictive Test Selection runs only the tests affected by a given change. Same coverage. Faster feedback. ML-trained on your build history. develocity.ai/product/predic… #CI #testing #DPE

#Gradle dependency locking for reproducible builds: // gradle.properties org.gradle.dependency.verification=strict dependencyLocking { lockAllConfigurations() } Pins transitive versions. Prevents silent upgrades. Required for any serious supply chain story. #DevSecOps

You never chose gradle/actions. You clicked "Set up a workflow," took GitHub's suggestion, and have run it on every commit since. 45,000+ repos got there the same way. 👇 blog.gradle.org/running-gradle…

Ephemeral CI runners re-resolve deps from scratch on every build. At AI commit volume, that egress adds up fast. #Develocity Artifact Cache serves deps locally — fast, low-egress, provenance intact. gradle.com/blog/artifact-… #AI #CI #DevOps