This message was deleted.

Hi @René - I can say reasonably concrete. For our Gradle stream it’s currently second on our list of major priorities, after some preparatory work for configuration caching. We intend to be starting on this in some form in this quarter, with initial delivery some time later in the year. It would be very helpful if you could share what kind of information you are wanting to see.

Hey Luke, thats sounds good. The information we'd like to see are details like transform class, start time / duration, cache information (e.g why not cached / savings, cache key ) We have quite some gaps in our GE timeline view caused by artifact transforms. Having those transforms grouped by configuration would also be interesting but not a priority

René suggestions would help me too. Right now, I have this task with UP-TO-DATE check that took 1m35s because of artifact transformation, but I can't understand what caused the artifact transformation and why isn't it cached (just like René)