Gradle Releases 9.9.0-RC1 With Test Filtering Fixes
The prerelease candidate targets build-script delays and test selection for large Java builds ahead of a stable version.
Updated on Nov. 2, 2026 in Software
Gradle released candidate version 9.9.0-RC1 on October 30, a prerelease that extends test filtering to JUnit Platform tests not declared as methods. The latest stable Gradle release is 9.8.2.
Why it matters
The candidate targets recurring work for Java teams maintaining large or customized builds, where test selection and retry behavior affect how long builds take to run. Tools that match problem identifiers or extract embedded report data may need adjustments when the update arrives.
The release notes report 65% faster script recompilation in one large multi-project build test compared with prior behavior, though results outside that test are not reported. Gradle 9.9.0-RC1 is a prerelease, and the latest stable version remains 9.8.2.
The players
Gradle
Gradle is an open-source build automation tool widely used to build and test Java and other JVM-based software projects.
The details
The candidate extends test filtering to JUnit Platform tests not declared as methods, including ArchUnit rules on fields and Spek scopes, by matching them using their enclosing class and the name reported by the test engine. It also limits Test Retry plugin reruns of non-method tests to failed tests, where previously every non-method test reran when any test in a task was retried. The incubating Problems API gains a predefined grouping hierarchy, and Gradle now regenerates the distribution URL for the requested version, so a custom download host is not retained automatically.
Timeline
October 30: Gradle 9.9.0-RC1 released as a prerelease.
November 2: Coverage of the Gradle 9.9 candidate published.
The Tech Race
Build tools compete on how precisely they can select and rerun tests as Java test frameworks such as JUnit Platform, ArchUnit, and Spek diversify how tests are declared. The candidate extends Gradle's filtering to non-method tests in that ecosystem, narrowing a gap that previously forced broader reruns.
Developers maintaining large or customized Gradle builds may see shorter test-selection and retry behavior in the candidate, but only after testing it against their own setups. Teams using custom download hosts will need to reconfigure them, since the distribution URL is now regenerated automatically.
The takeaway
Before upgrading to a candidate build, teams relying on custom download hosts or on tools that parse Gradle problem identifiers should verify their configuration against the prerelease. Testing on a representative build avoids surprises when the stable release arrives.
Further reading
For related coverage of developer tooling, explore the Software section.
Source note: This article includes information reported by ADTmag.
