After you have setup a local master, you need to add your own builders and run them locally before submitting it to the public buildbots.
...
Assuming your builder is correct and accessible, you should add your slave to the master's configuration and connect a builder to it.
Adding a slave
To add a slave, edit the configuration file:
~/buildmaster/config/slaves.py
...
create_slave("linaro-dragon-01", properties={'jobs' : 4}, max_builds=1),That means 4 threads (-j4) and one build at a time. Since this is a quad-core machine and the build normally uses 100% of the system, that's a good value.
Other possible values is "jobs=2, builds=2", which would underutilise the board if only one build is active at a time, but would be a good value if both builds are always running and they can take a bit longer (for example, on odd configurations that we only need to test once a week or less).
Another idea is to keep jobs=4 and builds=1 but connect two builders on the same bot on the builders.py file (see below). This would intercalate the builds based on each builder's queue. If one queue is empty, it builds again the same builder with the new commits. This is useful for a number of quick builds (without "make clean", or running "ccache"), but it reduces the utility of a fast build.
Adding a builder
Edit the file:
~/buildmaster/config/builders.py
Add a builder for your machine, for example:
{'name': "clang-cmake-thumbv7-a15-full",
'slavenames':["linaro-dragon-01"],
'builddir':"clang-cmake-thumbv7-a15-full",
'category': 'sanitizer',
'factory' : ClangBuilder.getClangCMakeBuildFactory(
jobs=4,
clean=False,
env={'PATH':'/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'},
extra_cmake_args=["-DCMAKE_C_FLAGS='-mcpu=cortex-a15 -mfpu=vfpv3 -mthumb'",
"-DCMAKE_CXX_FLAGS='-mcpu=cortex-a15 -mfpu=vfpv3 -mthumb'",
"-DCOMPILER_RT_TEST_COMPILER_CFLAGS='-mcpu=cortex-a15 -mfpu=vfpv3 -mthumb'",
"-DLLVM_TARGETS_TO_BUILD='ARM;AArch64;X86'"])},Quick explanation of the parameters:
- name: is what's going to be referenced on the website, example: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15
- slavenames: you can have more than one, if they're all identical. We have that for Pandas.
- builddir: where in ~/buildslave it'll build. This allows you to have different builds on the same machine.
- category: defines what repositories are monitored for changes. You'll have to look at the official config files to know that, but basically, "sanitizer" means llvm+clang+compiler-rt, while "clang" means only clang+llvm, etc.
- factory: which builder to use. That above is my own CMake builder. The arguments are:
- jobs: maximum number of jobs this specific builder will use. The "jobs" property on the slave (above) limits this number, but you can give priorities inside the same machine.
- clean: runs "make clean" or not
- env: self explanatory
- extra_cmake_args: self explanatory, can be found at: http://llvm.org/docs/CMake.html
...
Also, the LLVM admins belong to the buildslave group, so they can read/write to the build directories directly without needing sudo (most importantly to list files inside a directory). For that reason, you need to change the umask on the create-slave command line:
# Make sure you run this as the buildslave user!$ buildslave create-slave --umask=022 ~buildslave/buildslave slaveN.llvm.validation.linaro.org <buildslave-name> <password>
The slave will be compiling LLVM and other modules, so it'll need the minimum requirements like a suitable compiler, libraries and other tools to run the tests. Buildbot already needs python, so the make check should just work (it needs Python 2.7). The other packages you'll need are:
- build-essential (gcc, g++, binutils - preferably gold, etc)
- cmake, ninja-build, subversion
- libxml2-dev, zlib1g-dev, libtinfo-dev
And, if you need to run the test-suite:
- python-virtualenv
- bison groff gawk flex tclsh
To install buildslave and the dependencies, use Python's PIP, not apt-get:
$ pip install twisted==12.0 buildbot-slave==0.8.6 'sqlalchemy <= 0.7.10' To start the slave, just type:
$ buildbot start <slavedir>and you should see it online on your BuildMaster URL. If there are no commits it won't start building, but you can always press the build button on the bot interface to see what happens.
...
To do that, copy your changes back to the repository, separating patches to the builders and config in different branches (and pull requests), and making sure that config would work on your local build (or even another test build). In case everything works, submit a patch to llvm-commits@cs.uiuc.edu.
The buildmaster owner is Galina Kristanova, and once she picks up the config on to the master (either by you committing it or her), she'll restart the server and only then your changes will be available to all builders. So, you need to submit the requests in order, first changes to the builders, then changes to the configuration, then restart your buildslave pointing it to the public LLVM master instead of your local installation.