How do people get the Gradle caches, especially the

transforms

cache, under control? This regularly sucks away gigabytes of disk space with duplicated entries and has to be manually cleaned. I know that things (like for the DSL accessors) are stored by (hashed) classpath and I know Gradle tries to be rather fast and correct than memory-saving, but this situation is becoming unbearable. Once or twice a week I'm dealing with removing things from my 512G SSD just to keep things running.

https://docs.gradle.org/current/userguide/directory_layout.html#dir:gradle_user_home:configure_cache_cleanup you can tune the cleanup process

I recently came across https://github.com/rock3r/deep-clean 😬

This is my

~/.gradle/caches/9.5.0/transforms

directory and as you can see from the sheer block size there are many, many cache duplicates.

if you are making buildscript changes, that will happen (see the issue linked)

Yes, just read through it, this is exactly my issue. I wish Gradle would prioritize this.