What was shipped in Develocity 2026.3?
1️⃣ Artifact Cache now covers pip and Playwright.
2️⃣ Docker builds now produce a Build Scan.
3️⃣ Trusted Artifact Isolation splits the cache.
AND other goodies.
Which one are you going to try first? develocity.ai/releases/2026.…#WhatShipped#Develocity
Your agent passes its checks, but bugs still ship. More eyes on the PR won't help.
An AI that writes its own tests can pass them and still be wrong.
Use the test suite it didn't write, so green means go. develocity.ai/blog/regressio…#FromTheFounder#ContextEngineering
New IntelliJ IDEA Tech Talk episode!
@wolfs42, Principal Software Engineer at Develocity, joins @antonarhipov to investigate unnecessary task runs, check test history, and see how AI handles build problems in IntelliJ IDEA.
👉️ piped.video/xBNBjYH-foE 👈️
Agents can now upgrade your Gradle wrapper correctly using our new skill. We tested 7 models. How did they score?
0 of 7 models pinned it alone. With our skill, 4 scored 29/29. See the ranking: blog.gradle.org/introducing-…#HeadToHead#Gradle
ALT Bar chart titled wrapper-upgrade skill test results: 7 models, each with a without-skill bar (grey) and a with-skill bar (teal). Claude Opus 5.5 16 and 29, Gemini 3.8 Flash 15 and 29, DeepSeek V4 Pro 13 and 29, GPT 5.6 Luna 13 and 29, Claude Sonnet 5 12 and 28, Claude Haiku 4.5 10 and 26, Qwen 3.6 35B 12 and 17.
Your build passes, but it misses the cache on work that didn’t change. Logs don’t say why.
Two bytes change upstream and every downstream cache key resets, so you pay on every run. Build Scans show exactly which input changed. develocity.ai/blog/develocit…#WhatWeLearned#Develocity
ALT Screenshot of the Build Scan comparison from the javac blog: same task in both builds, 2 class files differ, so the cache keys differ. Numbered markers 1 to 3 point to each.
Gradle Skills 1.1.0 is out 🐘
• Best Practices skill now works better on weaker agents
• Wrapper Upgrade skill fixes rollback copy issues
Give your AI agent real Gradle know-how 👇
github.com/gradle/gradle-ski…
Your agents write fast. Then they wait on CI. Every failed build means more cost, more waiting.
Cache what hasn't changed. Run only the tests you need. Get back to shipping.
develocity.ai/blog/your-deve…#TheReframe#Develocity
Why does reading a clock slow your build down?
Gradle reads it constantly for traces and logs. On virtualized Windows that read is slow, and it compounds.
9.8.0 detects it at startup and switches source. Up to 45% faster there. docs.gradle.org/9.8.0/releas…#UnderTheHood#Gradle
ALT Two bars comparing the same build on a machine with a slow system clock. Before runs the full width in grey; after stops a little over half way in brand blue. Underneath, in the same blue: up to 45%.
Anthropic wrote the best case for getting Predictive Test Selection.
They proved test selection is mandatory at agentic volume, and what it costs to build your own. Which bucket do you fall in? Build your own OR buy from a vendor?
develocity.ai/blog/anthropic…#HotTake#Develocity
ALT Three bars showing how long each fix to a home-built test selection service lasted before it failed again: more cores 70 days, sharding 29 days, daily restarts less than 1 day. The last bar is a red sliver.
What does a self-propagating worm actually spend credentials on?
Publishing.
ChainDrop hit keyv, flat-cache and cache-manager in August. Develocity 2026.3 removes the static key, so a leaked credential can't fake trust.
develocity.ai/releases/2026.…#IncidentRead#ArtifactCache
ALT Three stages down a spine. A trusted build writes to the trusted namespace and reads only from it. An untrusted build reads both namespaces and writes only to the untrusted one. The release pipeline reads trusted only, so nothing from an untrusted build can reach it.
Gradle 9.8.1 delivers three high-severity security patches and fixes three regressions from 9.8.0: dependency resolution, toolchain detection on Debian and Ubuntu, and Quarkus test log capture.
docs.gradle.org/9.8.1/releas…#WhatsNew#Gradle
"We got only four cache hits on the first try." Anugrah Singha at DPE Summit.
Reaching 100% took declaring non-Java inputs and deleting out-of-band Maven scripts. Median build time is now 2.5 minutes. It started at 25.
Have you taken the first step?
#FromTheStage#DPESummit
ALT Anugrah Singha and Jason Erickson on stage at the DPE Summit, standing either side of a lectern with an Okta-stickered laptop on it, Erickson mid-sentence with a hand raised.
🔒 Gradle 8.14.6 is out with patches for 3 vulnerabilities, including fixes for unauthenticated deserialization and SSL repository handling. If you're on 8.14.x, upgrade now
docs.gradle.org/8.14.6/relea…#WhatsNew#Gradle
Where did an agent learn how your build works?
Questions tagged Gradle fell 98% in 3 years. Maven and Bazel too.
Developers stopped asking in public and started asking models. So are you getting the right context? develocity.ai/product/contex…#WhereTheLineGoes#ContextEngineering
Gradle 9.8.1 is out and there's 3 things you'll care about:
✅ Three high-severity holes patched. Upgrade if you run 9.x.
✅ Dependency resolution regression from 9.8.0, fixed.
✅ Quarkus test log capture, broken by 9.8.0, restored.
docs.gradle.org/9.8.1/releas…#WhatsNew#Gradle
Our caching agent will not do 3 things.
It does not modify custom plugins, change build logic unrelated to caching, or upgrade your build tool.
What it CAN do is name the input, reproduce the miss, and file the PR.
docs.develocity.ai/2026.3/in…#WhatWeDoNotCatch#Develocity
ALT Two dark slabs on pale paper, headed: where the agent stops. The upper slab, changes, reads build config and build scripts. The lower slab, refuses, reads plugins, unrelated logic, your Gradle version.
2 places to check your Maven CI time in under 1 minute.
1️⃣ Before the build: hit /actions/runs, subtract created_at from run_started_at.
2️⃣ Inside the build: add develocity-maven-extension to .mvn/extensions.xml, run mvn verify.
#DoItToday#Develocity
ALT Two windows in sequence. Before the build: a GET on /repos/OWNER/REPO/actions/runs, with created_at and run_started_at lit up in the response. Inside the build: .mvn/extensions.xml with the develocity-maven-extension lines being added.