Gradle uses lots of caches out of the box, but what if we added one more to make Gradle better? By default Gradle invalidates build cache as soon as anything is changed on the build classpath, be it your own build plugin or a version of an external plugin. That is a lot of potentially wasted effort to get identical outputs. What if we introduced a new cache that helped us survive build classpath changes? This talk will discuss creating such a cache, the ways to do it and what are the gains and costs in doing so.