This message was deleted.
# develocity
s
This message was deleted.
e
I think I understand your request, but could you please expand what you feature you would expect ideally in Gradle Enterprise, and how you'd like to use it?
c
An idea but is not the only way of using it: Each task in the scan to have the % of cache hit on a time range, and maybe the ability order tasks by it
e
What's the time range here?
c
I'm my case I want to detect which cacheable tasks are not getting any real improvement, so I can focus on look for the input changes
Time range.. last X hours/days
A more complex use case would be for a scan search, but I don't know how would I do a view for that
e
Would you want to customize the time range or set of builds for showing the cache hit %?
c
Ideally I would filter by CI tag
And maybe by the CI buildType
So..then yes, defining a time range is ideal
That said, even a non-filtered version could be an improvement
e
Understood. So the answer right now is "no, you'd have to do this analysis yourself using the GE API" but showing build cache usage across a filtered set of builds in our dashboards is high on the priority list
thank you 1
c
I think about it the next step after trends to see what tasks need to improve cacheability (or disable it)
e
yes
c
I have a ton of things to do, so it's not urgent, but it will help me a lot to understand the big picture without going task by task looking at the inputs.
e
Thanks for the feedback!