Add @DisableCachingByDefault as hint why outputs are not cached#1666
Merged
nedtwigg merged 5 commits intodiffplug:mainfrom Apr 6, 2023
Merged
Add @DisableCachingByDefault as hint why outputs are not cached#1666nedtwigg merged 5 commits intodiffplug:mainfrom
nedtwigg merged 5 commits intodiffplug:mainfrom
Conversation
Member
|
Thanks! |
Member
|
If you disagree with the changes I made above, please let me know. |
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.
The
@DisableCachingByDefaultannotation (JavaDoc) will make it easier to determine why this task was not cached when inspecting a Build Scan.Without this annotation, a gradle Build Scan will only show a generic message:
With the annotation, the Build Scan will show a more useful hint as to why this task was not cached: