This message was deleted.
# community-support
s
This message was deleted.
c
kinda, but not easily. by default the action caches pieces of the gradle user home - wrapper/dist, dependencies, build cache, configuration cache, etc. You can configure it to omit specific directories if you don’t want them. What is the use case for downloading dependency cache only and excluding other stuff?
c
I've caught gradle caching things and causing false positive builds before. I feel like it's CI's job to catch those things and CI passed too.
I want a fast build, and a slow build, but in both cases the downloaded artifacts should be fine
c
the cleanest way would be to run a separate build w/ say build cache, configuration cache disabled (either generate ~/.gradle/gradle.properties or -D options).
c
well, for the separate build I simply have a different job
c
yea, exactly, configure it as needed. remove dirs from gradle cache if need be or turn off build cache, etc.