How To Add Your Build Configuration To LLVM Buildbot Infrastructure


This document contains information about adding a build configuration and buildbot-worker to private worker builder to LLVM Buildbot Infrastructure.


There are two buildmasters running.

  • The main buildmaster at All builders attached to this machine will notify commit authors every time they break the build.

  • The staging buildbot at All builders attached to this machine will be completely silent by default when the build is broken. Builders for experimental backends should generally be attached to this buildmaster.

Steps To Add Builder To LLVM Buildbot

Volunteers can provide their build machines to work as build workers to public LLVM Buildbot.

Here are the steps you can follow to do so:

  1. Check the existing build configurations to make sure the one you are interested in is not covered yet or gets built on your computer much faster than on the existing one. We prefer faster builds so developers will get feedback sooner after changes get committed.

  2. The computer you will be registering with the LLVM buildbot infrastructure should have all dependencies installed and you can actually build your configuration successfully. Please check what degree of parallelism (-j param) would give the fastest build. You can build multiple configurations on one computer.

  3. Install buildbot-worker (currently we are using buildbot version 2.8.5). Depending on the platform, buildbot-worker could be available to download and install with your package manager, or you can download it directly from and install it manually.

  4. Create a designated user account, your buildbot-worker will be running under, and set appropriate permissions.

  5. Choose the buildbot-worker root directory (all builds will be placed under it), buildbot-worker access name and password the build master will be using to authenticate your buildbot-worker.

  6. Create a buildbot-worker in context of that buildbot-worker account. Point it to the port 9990 (see Buildbot documentation, Creating a worker for more details) by running the following command:

    $ buildbot-worker create-worker <buildbot-worker-root-directory> \
                 <buildbot-worker-access-name> \

    To point a worker to silent master please use instead of

  7. Fill the buildbot-worker description and admin name/e-mail. Here is an example of the buildbot-worker description:

    Windows 7 x64
    Core i7 (2.66GHz), 16GB of RAM
    g++.exe (TDM-1 mingw32) 4.4.0
    GNU Binutils 2.19.1
    cmake version 2.8.4
    Microsoft(R) 32-bit C/C++ Optimizing Compiler Version 16.00.40219.01 for 80x86
  8. Make sure you can actually start the buildbot-worker successfully. Then set up your buildbot-worker to start automatically at the start up time. See the buildbot documentation for help. You may want to restart your computer to see if it works.

  9. Send a patch which adds your build worker and your builder to zorg. Use the typical LLVM workflow.

    • workers are added to buildbot/osuosl/master/config/

    • builders are added to buildbot/osuosl/master/config/

    Please make sure your builder name and its builddir are unique through the file.

    It is possible to allow email addresses to unconditionally receive notifications on build failure; for this you’ll need to add an InformativeMailNotifier to buildbot/osuosl/master/config/ This is particularly useful for the staging buildmaster which is silent otherwise.

  10. Send the buildbot-worker access name and the access password directly to Galina Kistanova, and wait till she will let you know that your changes are applied and buildmaster is reconfigured.

  11. Check the status of your buildbot-worker on the Waterfall Display to make sure it is connected, and to see if administrator contact and worker information are correct.

  12. Wait for the first build to succeed and enjoy.