Sign in

Develocity

@gradle.com
340 followers 9 following 248 posts

Release announcements, tips, and events focused on boosting developer productivity with Develocity and Gradle.

PostsRepliesMedia
Develocity @gradle.com · 24/09/2026
📣 Gradle 9.8.0 is out! docs.gradle.org/9.8.0/release-notes… Bug fixes and… ☕ Java 27 support 🪞Maven mirror settings reuse 🔗 Linked problem locations in build output Please report any 🐛 on GitHub!
docs.gradle.org
Gradle 9.8.0 Release Notes
We are excited to announce Gradle 9.8.0.
010
Develocity @gradle.com · 22/09/2026
📣 Gradle 9.8.0 RC3 is out and ready for testing 🔬 docs.gradle.org/9.8.0-rc-3/release-… Bug fixes and… ☕ Java 27 support 🪞Maven mirror settings reuse 🔗 Linked problem locations in build output Please report any 🐛 on GitHub!
docs.gradle.org
Gradle 9.8.0-rc-3 Release Notes
We are excited to announce Gradle 9.8.0-rc-3.
011
Develocity @gradle.com · 18/09/2026
📣 Gradle 9.8.0 RC2 is out and ready for testing 🔬 docs.gradle.org/9.8.0-rc-2/release-… Bug fixes and… ☕ Java 27 support 🪞Maven mirror settings reuse 🔗 Linked problem locations in build output Please report any 🐛 on GitHub!
gradl.es
Gradle 9.8.0-rc-2 Release Notes
We are excited to announce Gradle 9.8.0-rc-2.
020
Develocity @gradle.com · 16/09/2026
Unpopular opinion: most caching problems aren't caching problems. They're "nobody looked at the Build Scan" problems.
010
Develocity @gradle.com · 15/09/2026
Cold starts on ephemeral CI runners are an underrated tax. Automated cache management landed in 2026.1; 2026.2 widened Artifact Cache and Setup Cache coverage. develocity.ai/releases/
develocity.ai
Develocity Release Notes | Develocity
Explore the release highlights or detailed release notes for a comprehensive view of Develocity updates and enhancements.
010
Develocity @gradle.com · 14/09/2026
Ran a benchmark on this: same model, only difference was access to real build data. 4/40 vs 36/40 on cache miss diagnosis. Numbers are wild. develocity.ai/blog/build-caching-optimizer-benchmark/
develocity.ai
What Build Data Adds to an AI Agent: A Benchmark | Develocity
Your AI agent can already read your build logs. We measured what changes when it can read your build data too: 36 of 40 runs solved, against 4.
000
Develocity @gradle.com · 11/09/2026
Cache hit rate is the number everyone quotes. Avoidable miss rate is the one worth acting on. One is a scoreboard. The other is a to-do list.
000
Develocity @gradle.com · 10/09/2026
Cache key debugging, the manual way: gradle build --scan Run it twice, from two different locations. Open both scans, diff the task inputs. That's usually where the volatile timestamp or absolute path is hiding.
000
Develocity @gradle.com · 09/09/2026
Build Caching Optimizer went GA for Gradle and Maven in 2026.2. Other toolchains aren't covered by the automated fix; you still get the Build Scan data, you just go find it yourself.
000
Develocity @gradle.com · 09/09/2026
We pointed a new agent-benchmarking harness at a real Gradle bug: Fable 5.1 vs Astra 6, same prompt, same 50-turn limit. Both fixed it (but not the same way). Diffs, cost, tokens, and which fix we're merging, on the blog: blog.gradle.org/two-agents-one-grad…
blog.gradle.org
Testing Astra 6 v Fable 5.1 on a Gradle docs bug
We gave two coding agents the same one-line Gradle documentation bug, the same repo, the same 50 turns, and a stopwatch. Both completed the task and fixed the bug. Here is everything that happened in ...
020
Develocity @gradle.com · 08/09/2026
📣 Gradle 9.8.0 RC1 is out and ready for testing 🔬 docs.gradle.org/9.8.0-rc-1/release-… Bug fixes and… ☕ Java 27 support 🪞Maven mirror settings reuse 🔗 Linked problem locations in build output Please report any 🐛 on GitHub!
docs.gradle.org
Gradle 9.8.0-rc-1 Release Notes
We are excited to announce Gradle 9.8.0-rc-1.
040
Develocity @gradle.com · 08/09/2026
📣 Gradle 9.8.0 RC1 is out and ready for testing 🔬 docs.gradle.org/9.8.0-rc-1/release-… Bug fixes and… ☕ Java 27 support 🪞Maven mirror settings reuse 🔗 Linked problem locations in build output Please report any 🐛 on GitHub!
docs.gradle.org
Gradle 9.8.0-rc-1 Release Notes
We are excited to announce Gradle 9.8.0-rc-1.
000
Develocity @gradle.com · 05/09/2026
Build Caching Optimizer went GA for Gradle and Maven in 2026.2. Other toolchains aren't covered by the automated fix; you still get the Build Scan data, you just go find it yourself.
000
Develocity @gradle.com · 01/09/2026
A build cache miss with zero explanation turned out to be two bytes, swapped, in javac's own output. Wildest root cause we've written up in a while. develocity.ai/blog/develocity-found-bug-java-compiler/
develocity.ai
How Develocity Found a Bug in the Java Compiler | Develocity
An unexplained Build Cache miss turned out to be a non-determinism bug in javac. Here is how comparing Build Scan data in Develocity found it.
010
Develocity @gradle.com · 31/08/2026
You patch your dependencies. You patch your images. You patch your CI runners. Who patches your build tool? Introducing the Gradle Security Subscription: fixes under SLA, coverage past end-of-life, and vulnerability disclosure before it's public. gradl.es/4A6WKbB
blog.gradle.org
Introducing the Gradle Security Subscription
The Gradle Security Subscription is available today: security fixes under an SLA, extended security maintenance, and advance notice of vulnerabilities ahead of public disclosure.
011
Develocity @gradle.com · 28/08/2026
Comparing two Build Scans is the fastest way to catch a path-dependent cache miss. Run the build from two locations, diff the task inputs. Usually, it's an absolute path or a volatile input hiding in there.
000
Develocity @gradle.com · 28/08/2026
We wrote up how a NullPointerException that fired 3,145 times over three months finally got tracked down. Two models, one build data source, no guessing. develocity.ai/blog/debugging-develocity-with-develocity/
develocity.ai
The Phantom Executor: Debugging Develocity with Develocity | Develocity
A NullPointerException fired 3,145 times over three months. Two AI models, a disciplined debugging method, and Develocity's own build data cracked it.
010
Develocity @gradle.com · 26/08/2026
An AI agent doesn't get tired of waiting on a slow build. It just hits the same wall again and again, immediately, all day. That's the part nobody priced in when they started pointing agents at CI.
020
Develocity @gradle.com · 26/08/2026
Flaky test flipping again this week. There's no build-config flag for this; quarantine runs off the Tests API. Read the test's outcome distribution, move it to a non-blocking suite above your threshold. Still runs, stops blocking merges. develocity.ai/product/flaky-tests-detection/
develocity.ai
Flaky Tests Detection | Develocity
Flaky Tests Detection identifies non-deterministic tests -- those that pass and fail under the same code and inputs -- and keeps their noise out of the CI signal
010
Develocity @gradle.com · 20/08/2026
Here's how to tag builds so you can actually query them later instead of scrolling through CI history: // settings.gradle develocity { buildScan { tag('release-candidate') tag('nightly') } } Future you will thank present you.
000
Develocity @gradle.com · 19/08/2026
Gradle is going agentic. Agents increasingly run, explain, and fix builds. We're making Gradle a build tool that agents can actually drive. It also meant postponing Config Cache by default: blog.gradle.org/gradle-is-going-age…
blog.gradle.org
Gradle Is Going Agentic
We're making Gradle work well with coding agents, and that meant not shipping Configuration Cache by default in Gradle 10 this cycle. Here's the tradeoff, and why we think it's the right one.
000
Develocity @gradle.com · 19/08/2026
📣 #Gradle 9.7.1 is out! docs.gradle.org/9.7.1/release-notes… Fixes regressions reported against 9.7.0. Report new 🐛 on GitHub!
docs.gradle.org
Gradle 9.7.1 Release Notes
We are excited to announce Gradle 9.7.1.
011
Develocity @gradle.com · 18/08/2026
Honest callout: caching only helps if your build is actually cacheable. Non-deterministic tasks — timestamps, random IDs, unordered outputs — still won't cache. Fix those first; no tool skips that step for you.
000
Develocity @gradle.com · 17/08/2026
AI coding tools 10x'd how much code gets written. Nobody 10x'd the CI fleet sizing to match. Guess which one everyone's complaining about.
000
Develocity @gradle.com · 14/08/2026
Small IntelliJ IDEA win for Gradle users: your version catalog accessors now show their resolved coordinates inline. api(libs.guava) → com.google.guava:guava:33.4.6-jre. No jumping to libs.versions.toml. 👌
0161
Develocity @gradle.com · 13/08/2026
Broken build script used to nuke your whole IDE sync -> 99 healthy projects go dark because 1 has a bad line. Gradle 9.7 + IntelliJ 2026.2 fix that. Resilient sync keeps completion alive in the file you're fixing. blog.gradle.org/resilient-sync
blog.gradle.org
Resilient Sync: Your IDE Keeps Helping even when your Build is Broken
Gradle 9.7 and IntelliJ IDEA 2026.2 bring resilient sync to IDE users. When part of your build fails to configure, Gradle still hands the IDE models for everything that succeeded, so you keep code com...
084
Develocity @gradle.com · 12/08/2026
A failing CI check knows exactly what broke. Usually it just says: red X, go read the logs. We taught the gradle/gradle bot to comment what actually failed, right on the PR. How we built it (and what we didn't ship yet): blog.gradle.org/dogfooding-failure-…
blog.gradle.org
The Red X that Says What it Saw
Develocity failure grouping now comments when a gradle/gradle pull request check fails. What the summary tells you on a real build failure, where its deep link takes you, and how it works.
000
Develocity @gradle.com · 11/08/2026
AI coding tools 10x'd how much code gets written. Nobody 10x'd the CI fleet sizing to match. Guess which one everyone's complaining about.
000
Develocity @gradle.com · 10/08/2026
Setup Cache now caches buildSrc and included builds, so configuration time isn't a tax on every ephemeral agent. No build-file change — it's delivered through the Artifact Cache CLI. Update the CLI to 1.3.0+; no Develocity upgrade required.
110
Develocity @gradle.com · 07/08/2026
The 2026.2 notes: Artifact Cache now covers SonarQube and Maven snapshots, and Setup Cache now covers buildSrc. Quietly one of the more useful releases this year. develocity.ai/releases/2026.2
develocity.ai
Develocity 2026.2
Release notes and updates for Develocity 2026.2
000
Develocity @gradle.com · 06/08/2026
Isolated Projects graduates from experimental to incubating in Gradle 9.7.0. Projects are configured in parallel. Gradle's own 300-subproject build saw median IDE sync drop from 84s to 47s. Config cache is a prerequisite. blog.gradle.org/introducing-isolate…
blog.gradle.org
Introducing Isolated Projects
Gradle 9.7.0 promotes Isolated Projects from experimental to incubating. The feature configures projects in parallel, making IDE sync and task runs significantly faster.
040
Develocity @gradle.com · 06/08/2026
📣 Gradle 9.7.0 is out! docs.gradle.org/9.7.0/release-notes… Bug fixes and… 🌱 Isolated Projects graduates to incubating ⚡ Broader Configuration Cache compatibility 🔍 More source locations in problem reports Please report any 🐛 on GitHub!
docs.gradle.org
Gradle 9.7.0 Release Notes
We are excited to announce Gradle 9.7.0.
030
Develocity @gradle.com · 05/08/2026
Every ephemeral CI agent starts from zero, every single time. We treat this like a law of physics instead of an actual solvable problem.
000
Develocity @gradle.com · 04/08/2026
Artifactory as the system of record, plus Develocity Artifact Cache serving builds locally, means faster builds without giving up provenance. Full write-up: develocity.ai/blog/artifact-cache-j…
develocity.ai
Why Artifact Cache and JFrog Artifactory are better together in the GenAI era | Develocity
AI surged code volume and made the CI pipeline the new bottleneck. Keep JFrog Artifactory as your system of record and add Develocity Artifact Cache to serve artifacts locally -- faster builds, lower egress, provenance intact.
000
Develocity @gradle.com · 03/08/2026
Artifact Cache isn't a build-file setting — it's a CLI step on your CI agent, served from a nearby Edge: # CI step, before the build artifact-cache restore --dv-server=https://develocity.example.com Restore deps before the build, store after. Your repo manager stays the system of record
010
Develocity @gradle.com · 31/07/2026
Real talk: flaky test detection tells you which tests are unreliable. It doesn't fix them for you. That part's still on your team — worth saying out loud.
000
Develocity @gradle.com · 31/07/2026
Debugging a build failure and debugging a flaky test are different skills. One is deterministic. The other is basically epidemiology.
100
Develocity @gradle.com · 29/07/2026
Quarantining a flaky test isn't giving up — it's triage: // build.gradle tasks.test { exclude '**/FlakyThing*' } Fix it properly later, off the critical path, without blocking everyone else's builds.
120
Develocity @gradle.com · 28/07/2026
The 2026.2 release notes are out. Buried in there: an agent that diagnoses cache misses for you instead of you doing it at 11pm. develocity.ai/releases/2026.2
develocity.ai
Develocity 2026.2
Release notes and updates for Develocity 2026.2
000
Develocity @gradle.com · 28/07/2026
Three Gradle talks from KotlinConf 2026, recapped so you can pick which ones deserve your 15 minutes. 1. Paul Merlin on the DSLs. 2. Stefan Wolf on 10 best practices. 3. Marcin Mycek on Declarative Gradle. blog.gradle.org/gradle-at-kotlincon…
blog.gradle.org
Three Gradle Talks from KotlinConf 2026 (and What to Steal from Each)
Recaps of the three Gradle talks from KotlinConf 2026, DSLs, best practices, and Declarative Gradle, with a few takeaways from each.
000
Develocity @gradle.com · 27/07/2026
The moment a team starts saying "it's probably just flaky" is the moment real regressions start hiding in plain sight. Flaky tests aren't harmless — they're a trust problem wearing a technical costume.
011
Develocity @gradle.com · 24/07/2026
If your team's default response to a red build is "just rerun it," read this before it gets worse: develocity.ai/resources/ebooks-and-…
develocity.ai
The Productive Developer’s Guide to Flaky Tests
Learn practical strategies for minimizing the negative impact of flaky tests and fostering a culture of test reliability.
001
Develocity @gradle.com · 23/07/2026
The Gradle team has been using Isolated Projects daily on our own build. Over six months: median IDE sync roughly halved (~1m24s → ~47s), and p95 dropped from ~7 min to just over 3. How we migrated and measured it: blog.gradle.org/isolated-projects-i…
blog.gradle.org
How the Gradle Team Adopted Isolated Projects
How the Gradle team adopted Isolated Projects as a daily driver, what we learned, and how we measured the impact.
040
Develocity @gradle.com · 22/07/2026
Our KotlinConf talk is up: A tale of the Gradle DSLs. Paul Merlin on how Gradle's build languages evolved -> Groovy, Kotlin DSL -> and where Declarative Gradle fits into what comes next. www.youtube.com/watch?v=k8T9IOnXPao
youtube.com
A tale of the Gradle DSLs | Paul Merlin
YouTube video by Kotlin by JetBrains
031
Develocity @gradle.com · 21/07/2026
Marcin Mycek's KotlinConf talk is up on YouTube: A First Look at the Kotlin Ecosystem Plugin for Declarative Gradle. If you've been curious what Declarative Gradle means for Kotlin builds in practice, this is the place to start: youtu.be/25Ngfn9Bhqc
youtu.be
A First Look at the Kotlin Ecosystem Plugin for Declarative Gradle | Marcin Mycek
YouTube video by Kotlin by JetBrains
010
Develocity @gradle.com · 21/07/2026
Here's a retry policy that actually works instead of infinite reruns: // settings.gradle develocity { testRetry { maxRetries = 1 maxFailures = 10 } } It caps the blast radius instead of hiding it forever.
000
Develocity @gradle.com · 18/07/2026
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-formerl…
blog.gradle.org
The Company Formerly Known as Gradle
Our company renamed itself from Gradle Technologies to Develocity. The Gradle Build Tool is not renamed, not acquired, and not relicensed. Here's what changed, what didn't, and why.
010
Develocity @gradle.com · 18/07/2026
📣 Gradle 9.7.0 RC1 is out and ready for testing 🔬 docs.gradle.org/9.7.0-rc-1/release-… Bug fixes and… 🌱 Isolated Projects graduates to incubating ⚡ Broader Configuration Cache compatibility 🔍 More source locations in problem reports Please report any 🐛 on GitHub!
docs.gradle.org
Gradle 9.7.0-rc-1 Release Notes
We are excited to announce Gradle 9.7.0-rc-1.
020
Develocity @gradle.com · 16/07/2026
Software shipped at human speed. AI just ended that. Gradle Technologies is now Develocity: same team and access, sharper focus on AI-driven delivery governance and efficiency. What changed and what stays the same: develocity.ai/blog/gradle-technolog… #Develocity #AI
000
Develocity @gradle.com · 16/07/2026
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-gradle-git…
blog.gradle.org
Triaging at Scale: How the Gradle Team Handles Issues and Pull Requests
Every issue and pull request on gradle/gradle now gets an answer within a week. Here is how we got there: retiring the stale bot, a response-time guarantee, triage automation, and what you can do to h...
010