Changes between Version 96 and Version 97 of SettingUpBuildslave

Timestamp:

06/29/22 11:54:40 (23 months ago)

Author:

Samuli Seppänen

Comment:

--

SettingUpBuildslave

@@ -69 +69 @@
 = Setting up a worker =
 
-=== Running buildbot as non-root user ===
+== Simplistic setup ==
+
+Note that Buildbot no longer supports Python 2.x, so ensure that your to-be worker has a working Python 3 installation.
+
+A simplistic procedure for Ubuntu 20.04 is described below. As t_client tests need root-level privileges anyways, here we show how to run a worker as root:
+
+{{{
+$ sudo -i
+$ apt-get install python3-pip
+$ pip3 install buildbot-worker
+$ mkdir /root/buildbot
+$ buildbot-worker create-worker /root/buildbot buildbot-host.openvpn.in:9989 worker-name worker-password
+}}}
+
+You can get the worker name and password from ''mattock''. Finally fill in the hostinfo files as described [https://docs.buildbot.net/current/manual/installation/worker.html here].
+
+Now you can launch the buildbot worker:
+
+{{{
+$ buildbot-worker start /root/buildbot
+}}}
+
+Check ''/root/buildbot/twistd.log'' to see if the worker was able to successfully connect to the master. Typically the error you see is an authentication issue:
+
+{{{
+2022-06-29 11:46:44+0000 [Broker,client] unauthorized login; check worker name and password
+}}}
+
+This can mean three things:
+* Your worker name is wrong
+* Your worker password is wrong
+* You worker has not yet been added to the buildmaster
+
+If advanced topics and troubleshooting help please refer to the official Buildbot documentation:
+
+* https://docs.buildbot.net/current/manual/installation/worker.html
+* https://docs.buildbot.net/current/manual/installation/installation.html
+
+== Running buildbot as non-root user ==
+
+'''NOTE:''' these instructions have not been tested with the current (3.x) version of Buildbot, but probably still work.
 
 Running buildbot as a root user is easiest, but you can tighten down the setup by giving a normal user limited super-user privileges.
@@ -84 +124 @@
 }}}
 
-
-
-== Configuring the buildslave for connectivity tests ==
-
-OpenVPN project's buildslaves run connectivity tests against several OpenVPN test servers on every commit. Due to these tests the openvpn instances launched by buildbot need to run as ''root'', or you need to configure ''sudo'' properly as described below.
+== Configuring a worker for connectivity tests ==
+
+OpenVPN project's workers run connectivity tests against several OpenVPN test servers on every commit. Due to these tests the openvpn instances launched by buildbot need to run as ''root'', or you need to configure ''sudo'' properly as described below.
 
 As the tests connect to remote OpenVPN servers you will need test certificates and a ''t_client.rc'' config file from the buildmaster admins (see above). Once you've have the files, put them to ''/home/buildbot'':
@@ -120 +158 @@
  * t_client test servers (listening on UDP and TCP ports 51194-51199)
 
-Once you're finished doing all of this, contact the buildmaster admins so that they can force a build (and the associated connectivity tests) on your buildslave. The first build is expected to fail, because the t_client.rc you were given first is a generic one. After the first build you can fix the values in ''t_client.rc'' file by looking at client test logs in ''<buildslave-dir/build/<buildername>/tests/t_client_<buildername>-<id>''. For example, for the Ubuntu 12.04 buildslave the build logs were in this directory:
+Once you're finished doing all of this, contact the buildmaster admins so that they can force a build (and the associated connectivity tests) on your worker. The first build is expected to fail, because the t_client.rc you were given first is a generic one. After the first build you can fix the values in ''t_client.rc'' file by looking at client test logs in ''<buildslave-dir/build/<buildername>/tests/t_client_<buildername>-<id>''. For example, for the Ubuntu 12.04 worker the build logs were in this directory:
 
 * /var/lib/buildbot/slaves/openvpn/build-ubuntu-1204-i386-stable-master/build/tests/t_client-ubuntu-1204-i386-20141217-160636
@@ -141 +179 @@
 
 = Troubleshooting =
+
+== Build failures ==
 
 In case your build fails, try running the same build steps manually to see what the problem is.