blob: f472f74e37cc14c9a95b4649549677c279a38678 [file] [log] [blame]
Galina Kistanovae30ba2e2012-09-13 23:51:08 +00001.. _how_to_add_a_builder:
2
3===================================================================
4How To Add Your Build Configuration To LLVM Buildbot Infrastructure
5===================================================================
6
Galina Kistanovae30ba2e2012-09-13 23:51:08 +00007Introduction
8============
9
10This document contains information about adding a build configuration and
11buildslave to private slave builder to LLVM Buildbot Infrastructure
12`<http://lab.llvm.org:8011>`_.
13
14
15Steps To Add Builder To LLVM Buildbot
16=====================================
17Volunteers can provide their build machines to work as build slaves to
18public LLVM Buildbot.
19
20Here are the steps you can follow to do so:
21
22#. Check the existing build configurations to make sure the one you are
23 interested in is not covered yet or gets built on your computer much
24 faster than on the existing one. We prefer faster builds so developers
25 will get feedback sooner after changes get committed.
26
27#. The computer you will be registering with the LLVM buildbot
28 infrastructure should have all dependencies installed and you can
29 actually build your configuration successfully. Please check what degree
30 of parallelism (-j param) would give the fastest build. You can build
31 multiple configurations on one computer.
32
33#. Install buildslave (currently we are using buildbot version 0.8.5).
34 Depending on the platform, buildslave could be available to download and
35 install with your packet manager, or you can download it directly from
36 `<http://trac.buildbot.net>`_ and install it manually.
37
38#. Create a designated user account, your buildslave will be running under,
39 and set appropriate permissions.
40
41#. Choose the buildslave root directory (all builds will be placed under
42 it), buildslave access name and password the build master will be using
43 to authenticate your buildslave.
44
45#. Create a buildslave in context of that buildslave account. Point it to
46 the **lab.llvm.org** port **9990** (see `Buildbot documentation,
47 Creating a slave
48 <http://buildbot.net/buildbot/docs/current/full.html#creating-a-slave>`_
49 for more details) by running the following command:
50
51 .. code-block:: bash
52
53 $ buildslave create-slave <buildslave-root-directory> \
54 lab.llvm.org:9990 \
55 <buildslave-access-name> <buildslave-access-password>
56
57#. Fill the buildslave description and admin name/e-mail. Here is an
58 example of the buildslave description::
59
60 Windows 7 x64
61 Core i7 (2.66GHz), 16GB of RAM
62
63 g++.exe (TDM-1 mingw32) 4.4.0
64 GNU Binutils 2.19.1
65 cmake version 2.8.4
66 Microsoft(R) 32-bit C/C++ Optimizing Compiler Version 16.00.40219.01 for 80x86
67
68#. Make sure you can actually start the buildslave successfully. Then set
69 up your buildslave to start automatically at the start up time. See the
70 buildbot documentation for help. You may want to restart your computer
71 to see if it works.
72
73#. Send a patch which adds your build slave and your builder to zorg.
74
75 * slaves are added to ``buildbot/osuosl/master/config/slaves.py``
76 * builders are added to ``buildbot/osuosl/master/config/builders.py``
77
78#. Send the buildslave access name and the access password directly to
79 `Galina Kistanova <mailto:gkistanova@gmail.com>`_, and wait till she
80 will let you know that your changes are applied and buildmaster is
81 reconfigured.
82
83#. Check the status of your buildslave on the `Waterfall Display
84 <http://lab.llvm.org:8011/waterfall>`_ to make sure it is connected, and
85 ``http://lab.llvm.org:8011/buildslaves/<your-buildslave-name>`` to see
86 if administrator contact and slave information are correct.
87
88#. Wait for the first build to succeed and enjoy.