Time Savings Report for Gradle and Xcode Builds

Changelog Build Cache
1

Description

New Time Savings Report for Gradle and Xcode Builds - Organizations trialing Bitrise Build Cache can now see exactly how much time Build Cache is saving their team with a new savings report for Gradle and Xcode invocations on both Bitrise CI and Build Hub.

pigroy
pigroy2460×1358 287 KB

Highlights:

  • Available During Build Cache Trials: This feature is now available for organizations trialing Build Cache. To get started, head over to Build Cache and add a new Gradle or Xcode connection.
  • See Total Time Saved: The new report calculates how much build time your team has saved by comparing build cache-enabled runs to baseline runs without build cache.
  • Built-In Baseline for Trials: For trialing organizations, the first build of each workflow is automatically marked as a baseline, and Build Cache is intentionally disabled for that run. This gives Bitrise a reliable reference point for measuring cache impact for each CI project and workflow.
  • Works on Bitrise CI and Build Hub: The savings report is available across both Bitrise CI and Build Hub, so teams using GitHub Actions through Bitrise can benefit from the same visibility.
  • Warmup Progress for New Connections: When creating a new connection, you’ll now see a warmup progress state until you’ve built the same workflow 10 times. Once enough data is collected, Bitrise unlocks:
    • Total time saved
    • Projected monthly savings
  • Top Commands by Savings: The report also highlights your top 3 Gradle or Xcode commands by total time saved, helping you quickly identify where Build Cache is delivering the biggest impact.
  • Better Guidance After Setup: Previously, after setting up a connection, users had less visibility into what to do next or when value would become visible. Now, the warmup state makes the next step clear: keep building, warm up the cache, and watch the savings grow over time.

Why This Matters

Build cache value compounds over time - but that value wasn’t always immediately visible after setup. With the new savings report, teams can now clearly track progress from the start, understand when the cache is warming up, and see concrete results as more builds run. Whether you’re on Bitrise CI or Build Hub, this makes it easier to prove ROI, drive adoption, and stay motivated during the first days of using Build Cache.

Bottom line: If you’re trialing Bitrise Build Cache, just add a connection in Build Cache to start tracking warmup progress and unlock a clear view into how much time Build Cache is saving your team.

1 Like