Make build work with Gradle config-cache and project isolation#891
Merged
Conversation
…reused because an input to unknown location has changed.`
dimas-b
approved these changes
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change adopts the build of the project to be fully compliant to Gradle's configuration cache and project isolation.
Using the configuration-cache is effectively prevented in CI as it can persist configuration inputs, which may include sensitive information.
The removal of the symlinked source directories had to be replaced with
Synctasks to preventCalculating task graph as configuration cache cannot be reused because an input to unknown location has changed.warnings / hints that config-cache isn't effective.Developers can add this line into the non-Git-tracked
.envfile to enable the config cache and project isolation locally:GRADLE_OPTS='-Dorg.gradle.configuration-cache=true -Dorg.gradle.unsafe.isolated-projects=true'Fixing the line-ending via spotless to
UNIXis necessary, because Spotless' default isGIT_ATTRIBUTES_FAST_ALLSAME, which reads repo config, user/system config,.git/info/attribtuesand more. Neither is config-cache-friendly - and leads to non-reused config-cache entries.