Today I went to the talk “Build systems à la carte” of Andrey Mokhov. He presented the results of the identically named paper from last year authored by himself and his co-authors. The following links point to the paper and its related resources:
- paper submitted to ICFP 2018
- presentation from ICFP 2018 by Simon Peyton-Jones (co-author)
- extended version of the original paper
- slides from today’s presentation (the talk was not recorded)
- code examples on GitHub
I had known about this paper from last year and I was excited to learn that Andrey was going to present this work at EPFL, Lausanne. In the next sections I summarize what I learned from the paper and the presentation.
The study explores the design space of build systems such as Make, Ninja, Bazel. Interestingly, through the lens of this paper, systems like Excel and Docker can also be seen as build systems.
Typically we specify our builds as a set of rules: we tell how a given target is built out of its dependencies. The build system’s job is to bring a specified target up-to-date. Depending on the application domain a build system may have some of the following properties:
- Minimality: don’t repeat work unnecessarily
- Early cutoff: stop when nothing changes
- Cloud builds: save repeating work by sharing build results among all developers
- Dynamic dependencies: some dependencies are not known in advance, but they are discovered as we run the build.
Two key design choices are typically deeply wired in any build system:
- Scheduling: the order in which tasks are built
- Rebuilding: whether or not a task is rebuilt
Today’s most commonly used build systems can be classified along these two axes. Let’s see these two aspects in detail.
Build systems use different strategies to execute the build tasks:
Topological: all the dependencies are known in advance. The tasks are executed in topological order. Examples: Make, Ninja, Buck
Restarting: if a task has an non-built dependency its build is aborted and restarted later when the dependency is available. Examples: Bazel, Excel
Suspending: a task is suspended when its build encounters a missing dependency. Examples: Shake, Nix
The chosen scheduling strategy has an effect on the properties of the resulting build system:
A topological scheduler cannot support dynamic dependencies. A topological order can only be established if all the dependencies are known at the beginning of a build.
Build system using restarting schedulers are not minimal because some work is repeated when restarted. Note that the cost of duplicate work may often be just a fraction of the overall build cost.
A suspending scheduler is theoretically optimal, but it is only better in practice than a restarting scheduler if the cost of avoided duplicate work outweighs the cost of suspending tasks.
We find the following techniques to decide whether or not a task is rebuilt:
Dirty bit: anything that changed since the last build is marked dirty (Excel, Make)
Verifying traces: rebuild a target if the values/hashes of the its dependencies changed since the last build (Ninja, Shake)
Constructive traces: like verifying traces, but also store the resulting target value. The stored value can be shared with other users. (Bazel)
Deep constructive traces: like constructive traces, but only store terminal input keys ignoring any intermediate dependencies (Buck, Nix)
Again, picking a given rebuilding strategy has interesting consequences:
- We can achieve minimality using dirty bits.
- It’s possible but hard to support early cutoff with dirty bits. Make approximates early cut-off.
- All traces support dynamic dependencies and minimality
- All traces except for deep traces support the early cutoff optimization
- Constructive traces enable cloud builds
- Deep constructive traces cannot support early cutoff
- Deep constructive traces may generate frankenbuilds if the tasks are not deterministic
Executable build system models
After a detailed classification of build system the authors present executable Haskell code to model real-world build systems. The concrete implementations are broken down into two components: Scheduler and Rebuilder, Here are some models in their final form:
make = topological modTimeRebuilder excel = restarting dirtyBitRebuilder shake = suspending vtRebuilder bazel = restartingQ ctRebuilder
It’s remarkable that the concepts presented in this work lead such succint implementations. The actual executable code can be found in this repository.
The work “Build systems à la carte” from Andrey Mokhov and his co-workers taught me a lot about how build systems work. It demonstrates the power of Haskell as a modeling language. I recommend you to read the paper and study the related resources shown at the beginning of this article.