-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kotlin-dsl not reusing configuration-cache in clean builds #21265
Comments
I've noticed this today in my project - apparently Gradle 8.1.1 is still affected by this issue |
Still encounter this when using Gradle 8.4. Is there anything we can do to push investigation of this forward? |
After running https://gist.github.com/myniva/80b9f98b7eac5b55584d2d1f536b23d5 I've noticed that for
Probably they are not cached, so when the clean build is run after restoring the cache on CI, they are missing, so configuration cache detects them as changed inputs? |
In my case the workaround was to cache |
Sorry for the late reply. Thank you for providing a valid report. The issue is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before a fix is made. |
Gradle 7.5 release announced that kotlin-dsl is CC compatible, but I have found an issue.
Using an included build to create a convention plugin, written with kotlin-dsl, I want to reuse CC in clean builds.
an easy example would be:
running
./gradlew help
, cleaning the build folders, and running./gradlew help
The use case is for CI, where the build always start from a fresh clone but the setup is absolutely identical, but it happens locally too.
Expected Behavior
Current Behavior
Context
Enabling CC in our CI is useless as it's never reused.
Steps to Reproduce
reproducer: https://github.com/CristianGM/kotlin-dsl-CC-issues
clone
execute
./gradlew help
, CC will be storedrunning
./gradlew help
will reuse CCdrop sample-plugin build folder:
rm -rf gradle-plugins/sample-plugin/build
execute
./gradlew help
, you'll see the message:Your Environment
I don't think my environment is relevant because I tried in different machines and OS
The text was updated successfully, but these errors were encountered: