As part of our project we use Bazel to build several targets and run tests that depend on such targets. Those targets in turn depend on external libraries which can certainly take a while to download and build (e.g. Boost, LLVM, etc.).
Given that Bazel already supports caching natively (through a remote caching architecture), is there a way for Travis to leverage this in order to reduce execution times for our tests? We’re currently getting a timeout in our CI runs because of Bazel will attempt to build our external dependencies every time.
PS: we’re trying to address timeouts in additional manners like using pre-built Docker images, but these’ll only help to a certain extent since Bazel builds/tests rely on the project’s source code and need to be executed on each code change.