Login

u/Party_Till_I_Die

r/Kotlin r/KotlinMultiplatform r/gradle r/androiddev r/java
▲ 14 r/Kotlin

Building a set of Gradle Agent Skills

I work at Gradle, and we are building agent skills. We have five candidates:

  1. Run Gradle correctly (gradle-cli) — right task, right flags, version-aware
  2. Best-practices lint (gradle-bestpractices) — flag legacy patterns, suggest the current one
  3. New project bootstrap (gradle-init) — KMP scaffold, version catalog, convention plugins
  4. Upgrade + deprecations (gradle-update) — bump the wrapper, rewrite what broke
  5. Configuration cache migration (gradle-cc) — find what breaks CC, refactor it

Which of these would you actually use? What's missing?

reddit.com
u/Party_Till_I_Die — 24 hours ago
▲ 3 r/androiddev

Which Gradle task would you hand off to an AI agent?

I work at Gradle, and we're building agent skills. We currently have five candidates:

  1. Run Gradle correctly (gradle-cli) — right task, right flags, version-aware
  2. Best-practices lint (gradle-bestpractices) — flag legacy patterns, suggest the current one
  3. New project bootstrap (gradle-init) — Android/KMP scaffold, version catalog
  4. Upgrade + deprecations (gradle-update) — bump the wrapper, rewrite what broke
  5. Configuration cache migration (gradle-cc) — find what breaks CC, refactor it

Which would you actually use? What do you want to see instead?

reddit.com
u/Party_Till_I_Die — 24 hours ago
▲ 5 r/gradle

Gradle Agent Skills Vote

We're building a set of Gradle Agent Skills. There are five candidates below:

  1. gradle-cli — Run Gradle the right way. Teaches the agent correct ./gradlew invocation: which task to run, which flags matter, what's version-specific, and how to read the output. No more --stacktrace on everything and hoping.
  2. gradle-bestpractices — Lint your build against current conventions. Scans your build logic and flags what's off: legacy APIs, subprojects {} sprawl, misused configurations, and missing version catalogs. Points to the current recommended pattern for each finding.
  3. gradle-init — Bootstrap a new Gradle project. Sets up a working project from scratch: sensible defaults, version catalog, and a starter layout for KMP, Android, or Spring. Skips the hour of copy-pasting from an old repo or adding random libraries.
  4. gradle-upgrade — Upgrade Gradle and clear deprecations. Version-aware upgrade path: bumps the wrapper, finds deprecated usages in your build logic, and rewrites them for the target version. Handles the multi-step hops so you're not stuck three majors behind.
  5. gradle-cc-migrate — Make your build Configuration Cache compatible. Reads your build logic, finds what breaks the configuration cache, and refactors it — script-level state, Project access at execution time, non-serializable task inputs. The single biggest build-speed win, minus the archaeology.

Which would help you most? Which one would you actually use? Do you have a better idea?

reddit.com
u/Party_Till_I_Die — 24 hours ago
▲ 18 r/gradle

Resilient Sync in Gradle 9.7 and IntelliJ 2026.2

Until now, a single broken build script would fail the entire sync. Every script turned red and no more autocomplete.

Resilient sync fixes this. Gradle builds tooling models for every project that configured successfully and reports only the failures, so one broken convention plugin no longer takes down the other projects. You keep code completion and highlighting in the build logic you're repairing.

Write-up here: https://blog.gradle.org/resilient-sync

u/Party_Till_I_Die — 7 days ago
▲ 23 r/gradle

IntelliJ now displays the Gradle version catalog data as hints

Small IntelliJ IDEA win for Gradle users: version catalog accessors now show their resolved coordinates inline.

u/Party_Till_I_Die — 8 days ago
▲ 27 r/androiddev

Isolated Projects incubating in Gradle 9.7.0 (AndroidX sync 4m00s → 2m47s)

Isolated Projects moved from experimental to incubating in Gradle 9.7.0.
When it's on, each project is isolated from the others, which lets Gradle configure them in parallel instead of one at a time:

  • AndroidX (1,000+ projects): Gradle's portion of Android Studio sync 4m00s → 2m47s
  • An Android monorepo of 5,000+ projects: full Android Studio sync 5m09s → 2m44s

AGP and KGP are compatible, but other Gradle plugins may not be. "Now in Android" was made compatible if you want a reference build.

Blog Post: https://blog.gradle.org/introducing-isolated-projects
Gradle 9.7.0 Release Notes: https://docs.gradle.org/current/release-notes.html

u/Party_Till_I_Die — 14 days ago
▲ 49 r/gradle+1 crossposts

Isolated Projects is now incubating in Gradle 9.7.0

Isolated Projects moved from experimental to incubating in 9.7.0. With it enabled, each project in a build is isolated from the others, which lets Gradle configure them in parallel.

Some numbers from the blog post:

  • Gradle's own build (300 subprojects): median IDE sync 84s → 47s
  • A 2,500-project Java monorepo: configuration with build-script recompilation 10m53s → 2m59s
  • An Android monorepo of 5,000+ projects: Android Studio sync 5m09s → 2m44s

Configuration Cache is a prerequisite.

You can enable it with org.gradle.isolated-projects=true in gradle.properties.

Here's the full blog post: https://blog.gradle.org/introducing-isolated-projects.

u/Party_Till_I_Die — 14 days ago