[]

FasterCI for Bazel

It is optimized to run bazel. Other build systems may also benefit from it as well, depending on the build workload. FasterCI for Bazel is achieving exceptional performance by using persistent runners, aggressive caching and optimized hardware.

Persistent runners are long running instances that keep the filesystem and running processes between different runs of the same workflow. They are created once and they are kept running for a long time.

Also, FasterCI provides a robust build cache that Bazel can really benefit from.

It is not uncommon to see 10x-60x speedups in Bazel builds compared to running them in a traditional CI/CD system.

Custom Bazel Configuration

FasterCI automatically generates a ~/.bazelrc file for your build to configure caching and reporting. If you need to provide additional Bazel configuration flags, you can create a file at .fasterci/bazelrc in your repository.

FasterCI includes this file using try-import, so it will be used if present:

try-import %workspace%/.fasterci/bazelrc

FasterCI for Bazel uses its own FasterCI Configuration Language. It is simple but powerful. It has distinct advantages like bazel automatic configuration, more strict security restrictions, etc.

Can't find what you're looking for? Please contact us so we can update the documentation. Thanks!

FasterCI builds