I've briefly discussed Gradle caching with one or two different people from Gradle at conferences that I was attending. I don't have any discussion notes to share. I thought that Gradle caching sounded interesting, but I don't expect that the Jenkins infrastructure team will have time to do anything with Gradle Develocity in the next 6 months.
We have received a $60k donation from AWS and need to make the necessary infrastructure changes to use that $60k donation. We need to continue our cost improvement efforts with Azure. We need to continue our work with DigitalOcean, with mirror providers, and with many others.
My initial interest was in finding ways to reduce the amount of testing that we perform without reducing the usefulness of the testing we perform. Gradle build caching did not seem to be a direct solution to that need. We're using Launchable with Jenkins core already and have seen good results from its test reduction techniques. The initial discussions seemed to indicate that Gradle's test avoidance techniques might not work very well with the Maven development environment used by Jenkins. I did not involve them in a detailed technical evaluation, just a brief conversation at one or more conferences.
I'm not aware of any public discussions either.