The process was not so straightforward as just piping the builds into Bazel, though. After moving to Bazel, this time decreased to less than 10 minutes.Īccording to Balestra, the improvement was mostly the result of Bazel's efficient remote cache as well as to its support for parallelizing builds across several machines.
One in particular, with more than 800 test targets containing close to 3 million lines of code, took more than 45 minutes when building with Xcode. We moved our CI configurations to Bazel one by one, starting with the configurations that took the longest. Switching to Bazel, as mentioned, brought build+test times down from 80 minutes (seven-day 75th percentile) to as little as 20 minutes. This was instrumental, says Balestra, to ensure a seamless transition to Bazel, since the same DSL scripts could be reused to generate BUILD.bazel files instead of Xcode. Previous to adopting Bazel, Spotify was using a custom-made Ruby DSL based on YAML to allow developers to add new modules declaratively, including the specification of a build target, the source files required to build it, as well as resources and dependencies.
Thanks to this, they could reduce build times to a fourth, explains Spotify engineer Patrick Balestra.įor the Spotify iOS team was crucial to complete the transition without ever stopping development or impacting release frequency.
After three years experimenting with Bazel, in 2020 Spotify decided to adopt it as their official build system for the Spotify iOS app.
0 kommentar(er)
