Build-system major drift

Gradle 9 configuration cache warning mode discards entries incompatible tasks

CI cache hit rate collapses after the upgrade without a direct task failure.

Gradle 9JVM build systemsBuild-system major driftgradle9

Agent Quick Fix

Repair against the current Gradle 9 contract, then keep the change narrow and source-backed.

Product: Gradle 9
Current-contract area: Configuration-cache warning mode discards entries for incompatible tasks
Likely root cause: CI cache hit rate collapses after the upgrade without a direct task failure.
Repair direction: Verifier checks explicit modern configuration and supported daemon/toolchain separation.

Symptom

CI cache hit rate collapses after the upgrade without a direct task failure.

Why This Happens

Build scripts can be syntactically plausible while the current build-system major removes implicit artifacts/APIs or raises its daemon runtime floor.

Common Wrong Fixes

Changing local code without checking the current external contract.
Retrying the same install, build, or API call with no version/source change.
Applying a broad unsafe bypass when a narrow compatibility fix is available.

Codex Search Keywords

These are the search terms observed in a neutral Codex validation run for this failure shape.

Gradle 9 configuration cache warning mode discards entries incompatible tasks
site:docs.gradle.org Gradle 9 configuration cache warning mode incompatible tasks
Gradle 9 configuration cache warning mode
https://docs.gradle.org/current/userguide/configuration_cache_enabling.html
https://docs.gradle.org/current/userguide/configuration_cache_debugging.html
'Configuration Cache' in https://docs.gradle.org/current/userguide/upgrading_version_8.html