GH Action for gradle setup - is it needed if we us...
# develocity
e
GH Action for gradle setup - is it needed if we use Develocity? I mostly interested in caching like configuration cache.
I see gradle configuration run on CI even we use Develocity
Ah, looks like configuration cache sharing between machines is not yet stable
j
There is nothing like Remote build cache but for configuration cache. I think it would be amazing if the current remote build cache could handle the config cache too in the future.
e
Thanks! So gradle action that uses GH cache is one of non existing develocity way
j
Yep, but it is not enough if you are using included builds (if nothing has change recently)
You need to manually cache more files.
e
Lucky/Unlucky we use buildSrc for build logic
Oke, additionally it saves the downloading time for some tasks. I see we dropped some build times since local cache is available now.
g
Hello. This issue has additional info: Included builds or `buildSrc` containing build logic prevent configuration-cache reuse.
I think it would be amazing if the current remote build cache could handle the config cache too in the future.
We do too, actually 😄 We're working on expanding caching support much further for CI, which will include configuration cache: • Universal Cache: It’s time for fast, reliable, and cheap CI pipelines • Artifact Cache CLI User Manual