r/gradle • u/Party_Till_I_Die • Aug 12 '26
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.
r/gradle • u/Party_Till_I_Die • Aug 12 '26
Small IntelliJ IDEA win for Gradle users: version catalog accessors now show their resolved coordinates inline.
r/gradle • u/Party_Till_I_Die • Aug 06 '26
https://docs.gradle.org/9.7.0/release-notes.html
Bug fixes andβ¦
π± Isolated Projects graduates to incubating
β‘ Broader Configuration Cache compatibility
π More source locations in problem reports
Please report any π on GitHub!
r/gradle • u/Party_Till_I_Die • Aug 13 '26
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
r/gradle • u/argfile • Aug 16 '16
r/gradle • u/Party_Till_I_Die • Aug 06 '26
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.
r/gradle • u/Party_Till_I_Die • Jul 30 '26
Blog post with reviews: https://blog.gradle.org/gradle-at-kotlinconf-2026
YouTube links:
r/gradle • u/linchpiner • Jul 25 '17
The first part contains several ideas for using Gradle in a DevOps world. The ideal case for Gradle there is when existing teams use Gradle in a build process, or have great hand-on experience with Gradle, Groovy, Java or other JVM language. With Gradle, they can use various Java libraries to manage remote systems. Also, it's good as a DevOps "glue" for the existing tools and scripts. You can use Gradle to define task-based orchestration with multiple entry points and use a Gradle file from command line and from CI/CD pipelines (Gradle is a first-class citizen in Jenkins).
The second part primarily focuses on various ways to parametrize a Gradle project. the third is about doing the actual operations locally and remotely (bigger focus on SSH operations). The fourth part is about dynamic tasks in Gradle and how to use them to efficiently build flexible CLI tools.
r/gradle • u/Party_Till_I_Die • Jul 22 '26
Our company renamed itself from Gradle Technologies to Develocity. The Gradle Build Tool is not renamed, not acquired, and not relicensed. You can learn a little more here if you are interested: https://blog.gradle.org/the-company-formerly-known-as-gradle
r/gradle • u/urbanwarrior3558 • Jan 20 '21
explainshell.com is a really handy site where you paste shell code and it looks up the man page documentation for each command.
How about an explaingradle.com site where you paste in a build.gradle or settings.gradle or whatever and it explains each line for you.
Is it a dumb idea? I might code it if I've time.
r/gradle • u/Party_Till_I_Die • Jul 23 '26
IP is the next step in Gradle's evolution, so we wrote about how we adopted it as a daily driver, what we learned, and its actual impact: https://blog.gradle.org/isolated-projects-in-gradle-team
r/gradle • u/CLOVIS-AI • Mar 06 '26
The Gradle documentation doesn't always use the terms in the same way we do orally. What we tend to call a 'module' isn't really what Gradle calls a 'module', what Gradle calls 'a configuration' has nothing to do with 'the configuration', etc.
I wrote this article to bring all of these terms in a single place. Hope you learn something new!
r/gradle • u/HumorousHippoHugs • Mar 31 '24
r/gradle • u/Party_Till_I_Die • Sep 25 '26
https://docs.gradle.org/9.8.0/release-notes.html
Bug fixes andβ¦
β Java 27 support
πͺMaven mirror settings reuse
π Linked problem locations in build output
Please report any π on GitHub!
r/gradle • u/JourneymanGM • Aug 30 '19
r/gradle • u/fomofosho • Jul 20 '19
I find it frustrating that I can't make use of build scans, without also revealing confidential information about the builds I'm doing to gradle servers. Why does it work this way? Is this simply a way to incentivize people to purchase gradle enterprise? It seems like something that could easily be supported offline