https://gradle.com/ logo
Join Slack
Powered by
I'm confused on how is `org.gradle.caching=true` h...
# community-support
v
I'm confused on how is 
org.gradle.caching=true
helping? I mean, when I run a build twice, the second one reuses the outputs, it doesn't do a clean build so what is `org.gradle.caching=true`'s usecase exactly? (Discounting the remote ability; I'm talking local only)
r
It stores the cache-artifacts on machine a long term storage (IIRC 7 days by default) across different branches, it's non-volatile as compared to incremental cache artifacts stored in your projects build dir.
v
If you build different branches, or switch things back and forth, for example
The most value you indeed get when also using a remote cache, but even just local it can help much, but also depends on how you work
v
I see thanks!
although..when switching branches; and /build folder is in gitignore, then the build artifacts should not be claered; so then a cache hit should occur?
v
The cache is not in 
build
even if you delete it or do a clean build, you will have cache hits, that's the point. :-)
v
okay if the branches are very different I can see that helping; thanks!
v
Also if the branches are very similar and you use multiple worktrees
Open in Slack
PreviousNext
Powered by