# Build Cache for Gradle v3.6.5

**URL:** <https://discuss.bitrise.io/t/build-cache-for-gradle-v3-6-5/26257>\
**Category:** Changelog\
**Tags:** step-update\
**Created:** [September 9, 2026, 10:02am UTC](https://discuss.bitrise.io/t/build-cache-for-gradle-v3-6-5/26257 "2026-09-09T10:02:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [September 9, 2026, 10:02am UTC](https://discuss.bitrise.io/t/build-cache-for-gradle-v3-6-5/26257/1 "2026-09-09T10:02:17Z")

</div>

## What’s Changed

- Bump the Bitrise Build Cache CLI to v3.8.5.
- Gradle analytics now reports each build’s invocation once, and reliably. Builds previously opened a second backend stream at teardown that was never saved or acked, so they ended with `Invocation wasn't saved successfully` even though the invocation had in fact been reported. Alongside that, invocations could go missing entirely in build shapes that skip the usual teardown path — configuration-cache reuse, Isolated Projects, composite builds, and builds where every task was skipped or `--dry-run` — and the tail of a build’s task events and task IO could be dropped before the stream ended. All of these now report exactly one complete invocation.

> **[Release 3.6.5 · bitrise-steplib/bitrise-step-activate-gradle-remote-cache](https://github.com/bitrise-steplib/bitrise-step-activate-gradle-remote-cache/releases/3.6.5)**
>
> What's Changed
> 
> Bump the Bitrise Build Cache CLI to v3.8.5.
> Gradle analytics now reports each build's invocation once, and reliably. Builds previously opened a second backend stream at teardown tha...