From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Is there any specific reason why I don’t need to save on CI `gc.properties` as mentioned <https://docs.gradle.org/current/userguide/dependency_caching.html#sec:cache-copy|there>.
I want to be able to give ability to my jobs cleanup cache from time to time and as far as I understand - `gc.properties`  is a part that makes it possible.

GitHub Actions via the <https://github.com/gradle/actions/blob/main/docs/setup-gradle.md|setup Gradle action> handles caching of various artifacts and cleanup of the cache at the end of the build.

GitLab cache is basically zip everything related to cache entry and push to a storage (in our case S3). After some time gradle cache becomes too big and it takes too much time to download-&gt;unzip-&gt;build-&gt;zip-&gt;upload.