Build and test caching: Improve build and test performance by up to 10x
By acquiring the advanced caching and CDN technology of flare.build, Bitrise brings to market an uncontested build and test caching solution available nowhere else. The first of its kind, and fully managed by Bitrise requiring no setup or maintenance, you can use our out-of-the-box cache Steps containing all the code you need to perform build and test caching tasks at the highest velocity.
A drop-in solution for most build tools
Advanced, yet easy to use, our build and test caching support is a drop-in solution for the most popular build tools, eliminating the need for costly additional setup and infrastructure. By using our Build Cache Steps*, previously compiled outputs from previous CI jobs can be reused in your next build.
*Steps: Ready-to-use, out-of-the-box build tasks that require no setup, no maintenance, and all the code you need.
Reduction in data transfer costs
By utilizing co-located CDN edge nodes in our data centers and the public cloud, build speeds increase greatly and your bandwidth costs are reduced or eliminated entirely.
Unmatched performance benefits
Speed up feedback loops, iterate faster, and multiply app build performance by up to 10x. The technologies of flare.build and Bitrise provides the backbone for powerful performance enhancements to your mobile application CI workflows running on Bitrise. Mobile teams using our technology have reported up to a 94% reduction in build times.
Supercharge developers and CI
Reliable, shared artifact cache. Local developer workstations and CI jobs both can share the same build outputs and test results, maximizing cache hit rates and keeping build and test times low both in CI and local development.
About build and test caching
Different from dependency caching that caches third-party dependencies, Bitrise’s advanced build caching functionality allows for faster build and test runs by intelligently caching the built outputs of the modules and libraries that make up your application, generated when compiling your first-party code.
Test runs, like unit test runs, can also be cached using this approach (test avoidance) in some build systems (such as Bazel or Gradle). This means that tests that are unaffected by your code changes can avoid being rerun at all — resulting in massively reduced build and test times.
Additionally, local build and test performance can be improved by allowing developers direct access to the shared caching infrastructure managed by Bitrise–provided you’re using a supported build system.
Test runs, like unit test runs, can also be cached using this approach (test avoidance) in some build systems (such as Bazel or Gradle). This means that tests that are unaffected by your code changes can avoid being rerun at all — resulting in massively reduced build and test times.
Additionally, local build and test performance can be improved by allowing developers direct access to the shared caching infrastructure managed by Bitrise–provided you’re using a supported build system.
Types of caching solutions from Bitrise
Bitrise offers two types of caching solutions:
Build and test caching
The first of its kind, and 100% managed by Bitrise requiring no setup or maintenance, you can use our out-of-the-box cache Steps to cache your build and test tasks or artifacts at the highest velocity. Our world-class CDN ensures that your cache is stored right next to where it is needed by the machines running those builds, which provides additional speed gains.
Talk to usDependency caching
Dependency caching is used to cache your third-party dependencies. Your workflow runs will save your dependencies for fast reuse so that they need not be downloaded off the internet every time the workflow is run. Bitrise supports preconfigured caching steps for major package managers and generic caching steps that allow you to customize your caching and support any package manager of your choice.
Learn more
