Ability to compare local results with cached results for task about gradle

[lptr]

We should also provide a way to display the stored meta-data (and the one we'd be storing instead with the current execution maybe).

[wolfs]

Ideas:

• Download entry from the cache and expand it on the local disk for a given task with its cache key
• Do the same with a given cache key for a task
• We should have the same structure for the outputs on disk and the downloaded result from the cache

[lptr]

Producing the same structure for the locally executed task and the downloaded result has some advantages:

• it's easy to compare with a third-party tool, even if there are multiple output properties
• once we have meta-data as part of the cached results (see https://github.com/gradle/build-cache/issues/86), those can also be compared as files

[lptr]

So how could a tool like this help us diagnose why Siri's JavaCompile tasks are not cached (see https://github.com/gradle/build-cache/issues/218)?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[stale]

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.