Description
The Bitrise Build Cache savings report for Gradle and Xcode invocations is now available to all Build Cache customers, including subscribers. This means teams can continue tracking how much time Build Cache saves over time, not just during the trial period.
Highlights:
- Now available for subscribers: Previously, the Time Savings Report was primarily a trial experience. Now Build Cache subscribers can also keep seeing Total time saved, helping continuously validate the value of their investment.
- Still visible after trial expiry: If your Build Cache trial ends, the report does not disappear immediately. For up to 180 days after trial end, the report and Build Cache Insights continue showing your trial results so you can evaluate ROI with real data.
- Fresh baselines every 30 days: Savings are no longer measured forever against a single old baseline build. Each workflow now gets a refreshed baseline once its current one becomes older than 30 days, so reported savings better reflect how your project builds today.
- Smarter baseline refresh behavior:
- Only one build at a time runs as a baseline, so parallel builds of the same workflow are not all left uncached
- Baseline refreshes are spread out over time, so they do not all happen at once
- Workflows with fewer than 10 builds in 30 days keep their current baseline longer, avoiding disproportionate uncached runs
- Projected monthly savings shown more appropriately: This metric is now shown only for periods shorter than 30 days. For longer periods, showing the projection would simply repeat the total.
Bug fixes:
- Clearer reporting periods: Savings cards now show the actual period their numbers cover, such as Trial period so far, Last 30 days of your trial, Trial period, Usage period, or Quota usage.
- More consistent post-trial Insights: Build Cache Insights now continues showing cache hit rate after a trial ends, and no longer incorrectly states that cache downloads are unlimited once the trial is over.
Why This Matters
Build Cache value should not disappear from view once a trial ends or a subscription starts. By extending the Time Savings Report to subscribers and keeping trial results visible after expiry, Bitrise makes it easier to measure ongoing impact, validate ROI, and understand whether Build Cache continues to deliver value as your codebase evolves.
Bottom line: Whether you’re trialing Bitrise Build Cache or already subscribed, you can now keep tracking how much time it saves your team, with fresher baselines and clearer reporting periods to make those numbers easier to trust.