bazel-buildfarm VS llama

It can be. By default it is local.

But it has protobufs interfaces (IIRC), so a distributed build farm would generate the grpc endpoints for their implementation and then you tell bazel on the command line (or via .bazelrc) the address of the build farm it can use.

There's a couple of projects that implement the distributed/grpc part, the main one is https://github.com/bazelbuild/bazel-buildfarm

Not sure what to say concerning buildfarm's remote execution.

Reading an issue I've opened 1y ago [1], seems the backend requires the client to have a specific gcc version.

That's a strong limitation imho.

[1] https://github.com/bazelbuild/bazel-buildfarm/issues/545

You can also set up a remote build service that uses the same environment you run the containers in using something like https://github.com/bazelbuild/bazel-buildfarm

Currently migrating to Bazel + bazel remote execution via Bazel buildfarm. Bazel has native support for build clusters.

I was surprised there wasn't a more obvious link, but the implementation of the ideas in the post is in open-source CLI tool here https://github.com/nelhage/llama

See also llama:

https://github.com/nelhage/llama

> Llama is a tool for running UNIX commands inside of Amazon Lambda. Its goal is to make it easy to outsource compute-heavy tasks to Lambda, with its enormous available parallelism, from your shell.