Build Cache for Gradle v3.6.3

Changelog
1

What’s Changed

  • Bump the Bitrise Build Cache CLI to v3.8.3, which brings common 1.0.9, remote-cache 2.1.1 and gradle-analytics 3.2.4.
  • Gradle builds now print a cache and a task summary at the end of the build: blob hits, lookups, distinct blobs and uploads from the cache plugin, and task hits over actionable tasks from the analytics plugin. Each cache service also logs a short id at startup and again with its stats, so a build log holding several of them can be read apart.
  • The task hit rate the Build Cache UI shows was too low and is now correct. Task outcomes were counted twice for any task that made the slowest-task list, and because slow tasks are rarely cache hits the duplicates landed in the denominator — one build reported 19.89% where 24.78% was true.
  • A colourised auth token no longer breaks Gradle analytics: an escape sequence in the token produced Unexpected char 0x1b at 7 in Authorization value and took the task-graph upload and the analytics stream with it.
  • Expect one build per datacentre to miss its task cache after upgrading. The analytics plugin contributes to each task’s cache key, so a plugin version change invalidates task entries once and that build re-seeds them.