You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A pretty clear warning message is produced (trimmed for readability):
=============================== Gradle Doctor Prescriptions
| The following operations were slower to pull from the cache than to rerun:
| :...:generateGitProperties
| Consider disabling caching them. |
| For more information see: https://runningcode.github.io/gradle-doctor/slower-from-cache/
Desired Behavior
It would be nice if the output contained a block of code that could be directly copypasted into the Gradle build file, to save an extra step of figuring out intermediaries (in this case, <taskname>, but other prescriptions will have different targets that are likely already available to Gradle Doctor internally).
The text was updated successfully, but these errors were encountered:
Gradle Doctor is already able to figure out which component is misbehaving (generateGitProperties), and how exactly (faster to rerun than to extract from the cache)
I don't know enough about Gradle to be 100% sure, but I would guess that there's a short traversable path from the user visible task name to its class, GenerateGitPropertiesTask
It should be simple, then, to modify the prescription so it reads something like this:
| The following operations were slower to pull from the cache than to rerun:
| :...:generateGitProperties| Consider disabling caching them.
| Add this block into your Gradle build file to achieve this:
tasks.named("<GenerateGitPropertiesTask>").configure {
outputs.cacheIf { false }
}
| For more information see: https://runningcode.github.io/gradle-doctor/slower-from-cache/
Existing Behavior
A pretty clear warning message is produced (trimmed for readability):
Desired Behavior
It would be nice if the output contained a block of code that could be directly copypasted into the Gradle build file, to save an extra step of figuring out intermediaries (in this case,
<taskname>
, but other prescriptions will have different targets that are likely already available to Gradle Doctor internally).The text was updated successfully, but these errors were encountered: