-
Notifications
You must be signed in to change notification settings - Fork 5k
Reuse CC upon unrelated changes to gradle.properties
#34712
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
base: master
Are you sure you want to change the base?
Conversation
|
@bot-gradle test ACC |
This comment has been minimized.
This comment has been minimized.
|
The following builds have passed: |
|
The following builds have failed: |
|
The following builds have failed: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
| outputContains "configuration cache cannot be reused because Gradle property 'foo' has changed." | ||
| } | ||
|
|
||
| def "invalidates cache when system property used at configuration time changes on disk"() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💅 Should we also test that we reuse the cache if the system property is never read?
| outputContains "configuration cache cannot be reused because Gradle property 'foo' has changed." | ||
| } | ||
|
|
||
| def "invalidates cache when system property used at configuration time changes on disk"() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💅 I would also add a test where a system property is set in the file, used only at execution time, to verify that the change to it is visible, while still getting a cache hit.
Fixes #20969
Reviewing cheatsheet
Before merging the PR, comments starting with