Conversation
Enable the Develocity remote build cache for all builds, with push limited to CI. This allows developers to reuse cached outputs from CI builds, reducing local build times.
|
Hi @JacquesLeRoux , thank you for the update. No rush, I completely understand it's not a pressing issue, just a quality of life improvement 👍 |
|
@ribafish Now that I’ve merged your other pull request #1028, which made the
However, our goal is to switch to the following as soon as we resolve some build issues:
My only concern is that merging this PR before we understand and fix the issues preventing us from running the new tasks might make it more difficult to debug why they fail on CI but succeed locally. Moreover, since I’ll try to investigate these issues, but if you have any advice, please let me know. Thank you in advance! |
Summary
Enable the Develocity remote build cache for all builds. Push is limited to CI (
GITHUB_ACTIONS), so CI populates the cache and developers benefit from it on local builds.The remote cache was explicitly disabled (
enabled = false). This change setsenabled = truewithpush = isCI, following the standard Develocity configuration pattern.