Skip to content

fix/gradle: don't skip the Kotlin config export for cached compiles - #1059

Merged
christoph-sg merged 5 commits into
mainfrom
ch/fix-kotlin-gradle-cache
Nov 4, 2026
Merged

christoph-sg merged 5 commits into
mainfrom
ch/fix-kotlin-gradle-cache

Conversation

@christoph-sg

@christoph-sg christoph-sg commented Nov 4, 2026 •

Copy link
Copy Markdown
Member

Register a scipKotlinConfigs task instead and finalize Kotlin compiles with it. As it doesn't declare outputs Gradle runs it every time and never caches it. Kotlin compilation itself stays cacheable.

register a scipKotlinConfigs task instead and finalize Kotlin compiles with it.
As it doesn't declare outputs Gradle runs it every time and never caches it.
Kotlin compilation itself stays cacheable.
christoph-sg and others added 4 commits November 4, 2026 14:30
When a run reuses the configuration cache entry of an earlier run, the
stored -randomtimestamp leaves compileJava up to date and no Java shards
are written. This test fails until that is fixed.

Amp-Thread-ID: https://ampcode.com/threads/T-01a1a699-5570-748e-af9d-6031d2964026
Co-authored-by: Amp <amp@ampcode.com>
The Gradle plugin isn't compatible with the configuration cache:
scipPrintDependencies uses the project at execution time, and a reused
entry keeps compileJava's random timestamp, leaving it up to date. The
CLI now passes --no-configuration-cache after the build command, so it
also overrides gradle.properties and a --configuration-cache in a custom
build command.
This reverts commit e976e40.

Not needed now that the CLI disables the configuration cache.
@christoph-sg
christoph-sg merged commit bdceafa into main Nov 4, 2026
29 checks passed
@christoph-sg
christoph-sg deleted the ch/fix-kotlin-gradle-cache branch November 4, 2026 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants