The Buildbarn project provides an implementation of the Remote Execution protocol. This protocol is used by tools such as Bazel, Buck2, BuildStream and recc to cache and optionally execute build actions remotely.
In bb-deployments you will find example configurations for a full Buildbarn deployment.
You can then have a look at bb-storage
to see the implementation of the storage daemon. Buildbarns components takes
only one parameter, the path to a configuration file. The schema for the
configuration files are described in .proto format and in the
proto files
you will find detailed descriptions for all of the options.
With bb-storage you can configure a load balanced remote cache solution for your builds after which you can then move on to bb-remote-execution and find the programs required for remote execution.
As your build grows large you can then set up a bb-clientd daemon on your workstation. This is an implementation of the remote output service based on Buildbarns storage implementation.
There is a #buildbarn channel on buildteamworld.slack.com that you can join to get in touch with other people who use and hack on Buildbarn.
Buildbarn has an active and enthusiastic community. Though we try to help and support those who have issues or questions, sometimes organisations need more dedicated support. The following is a list of community members who you can contact if you require commercial support. Please submit a PR if you wish to have your name listed here. Having a name listed is not necessarily an endorsement.
- Finn Ball - Freelance Consultant
- Fredrik Medley - Consultant
- SUE - Cloud Native Solutions - Support & Services Company
- Meroton - Cloud Hosted Buildbarn and Services
- SUE - Cloud Native Solutions - Support & Services Company
Buildbarn does not encourage commercial forks and is willing to engage with organisations to merge changes upstream in order to be maintained by the community.
