OLA Buildbot - Revision history

Peternewman: /* OpenBSD Instructions */ Add eg++ etc

2020-12-30T01:38:02Z

‎OpenBSD Instructions: Add eg++ etc

Peternewman: /* Enabling the Javascript Lint Checker */ More ways to install the linter

2016-02-14T21:15:17Z

‎Enabling the Javascript Lint Checker: More ways to install the linter

Peternewman: /* Prerequisites & Warning */ Update the configure options we run

2015-03-14T16:14:01Z

‎Prerequisites & Warning: Update the configure options we run

Peternewman: /* Prerequisites & Warning */ More info on passwords

2015-03-14T16:11:25Z

‎Prerequisites & Warning: More info on passwords

Nomis52 at 16:30, 28 December 2014

2014-12-28T16:30:11Z

Nomis52: /* Slave Configuration */

2014-12-28T16:28:33Z

‎Slave Configuration

Peternewman: More notes

2014-04-05T20:59:20Z

More notes

Peternewman: Update contact info

2014-04-05T15:16:32Z

Update contact info

Peternewman: /* Slave Configuration */ More detail

2014-04-05T15:07:07Z

‎Slave Configuration: More detail

RenZO: /* Build Slave Installation */

2014-04-05T14:43:34Z

‎Build Slave Installation

@@ Line 225: / Line 225: @@
 </pre>
-Export the variables needed for autoconf and configure on OpenBSD (add these to the .profile or equivalent for next time):
+Export the variables needed for autoconf and configure on OpenBSD (add these to the .profile or equivalent for next time), the eg++/egcc lines are needed if the installed gcc is too old to pass configure, install the eg++ one and then use that line:
 <pre>
 export AUTOCONF_VERSION=2.69
@@ Line 231: / Line 231: @@
 export CPPFLAGS="-I/usr/local/include/"
 export LDFLAGS="-L/usr/local/lib/"
 </pre>

@@ Line 334: / Line 334: @@
 The lint checker enforces Javascript style. We only run this once per change but it's good to have multiple lint-enabled hosts in case one is down.
-Install the gjslint checker by following the relevant instructions here (you man need to install python-setuptools to get easy_install on Debian/Ubuntu):
+Either:
-https://developers.google.com/closure/utilities/docs/linter_howto
+*Install the closure-linter deb package if it's present on your OS
 Finally let Simon or Peter know, or raise an issue, asking them to enable Javascript lint for your slave.

@@ Line 25: / Line 25: @@
 <pre>
 autoconf -i
-./configure --enable-e133 --enable-rdm-tests --enable-python-libs
+./configure --enable-e133 --enable-rdm-tests --enable-python-libs --enable-ja-rule
 make
 make check
@@ Line 32: / Line 32: @@
 cycle before proceeding. If you have trouble ask on the mailing list.
-If you're running the lint check, you need ccplint.py in your path somewhere, see README.developer for info on how to obtain it.
+If you're running the lint check, you need cpplint.py in your path somewhere, see README.developer for info on how to obtain it.
 Buildbot slaves need to connect to  buildmaster.openlighting.org:9989 . Make sure your firewall allows this. No port forwarding for inbound connections is required.

@@ Line 19: / Line 19: @@
 Slaves execute code directly from the git repo. Even though submits to the git repo are locked down, this is still a possible attack vector for your machine. For this reason it's best to run build slaves within a virtual machine.  TODO: link to some VM solutions.
-At the very least you should run the buildslave as a separate user (not root!). Slave passwords aren't stored in the git repo for security, you'll need to get Simon to add new ones.
+At the very least you should run the buildslave as a separate user (not root!). Slave passwords aren't stored in the git repo for security, you'll need to get Simon or Peter to add new ones.
 The buildbot performs full build & test runs with all the options enabled. Please make sure you have all the necessary libraries installed on your system. You need to be able to complete a

@@ Line 34: / Line 34: @@
 If you're running the lint check, you need ccplint.py in your path somewhere, see README.developer for info on how to obtain it.
-Buildbot slaves need to connect to  buildbot.openlighting.org:9989 . Make sure your firewall allows this. No port forwarding for inbound connections is required.
+Buildbot slaves need to connect to  buildmaster.openlighting.org:9989 . Make sure your firewall allows this. No port forwarding for inbound connections is required.
 == Debian / Ubuntu Instructions ==
@@ Line 110: / Line 110: @@
 Setup the slave itself:
 <pre>
-/usr/local/bin/buildslave create-slave ola-slave buildbot.openlighting.org:9989 <slave user> <slave password>
+/usr/local/bin/buildslave create-slave ola-slave buildmaster.openlighting.org:9989 <slave user> <slave password>
 </pre>
@@ Line 173: / Line 173: @@
 Setup the slave itself:
 <pre>
-/usr/pkg/bin/buildslave create-slave ola-slave buildbot.openlighting.org:9989 <slave user> <slave password>
+/usr/pkg/bin/buildslave create-slave ola-slave buildmaster.openlighting.org:9989 <slave user> <slave password>
 </pre>
@@ Line 235: / Line 235: @@
 Setup the slave itself:
 <pre>
-/usr/local/bin/buildslave create-slave ola-slave buildbot.openlighting.org:9989 <slave user> <slave password>
+/usr/local/bin/buildslave create-slave ola-slave buildmaster.openlighting.org:9989 <slave user> <slave password>
 </pre>
@@ Line 291: / Line 291: @@
 su ola-build-slave
 cd ~
-buildslave create-slave ola-slave buildbot.openlighting.org:9989 <slave user> <slave password>
+buildslave create-slave ola-slave buildmaster.openlighting.org:9989 <slave user> <slave password>
 </pre>

@@ Line 51: / Line 51: @@
 <pre>
-  sudo -u buildbot buildslave create-slave --usepty=0 /var/lib/buildbot/slaves/ola buildbot.openlighting.org:9989 <slave user> <slave password>
+  sudo -u buildbot buildslave create-slave --usepty=0 /var/lib/buildbot/slaves/ola buildmaster.openlighting.org:9989 <slave user> <slave password>
 </pre>

@@ Line 325: / Line 325: @@
 wget http://google-styleguide.googlecode.com/svn/trunk/cpplint/cpplint.py
 sudo cp cpplint.py /usr/local/bin
-chmod a+x /usr/local/bin/cpplint.py
+sudo chmod a+x /usr/local/bin/cpplint.py
 </pre>
@@ Line 334: / Line 334: @@
 The lint checker enforces Javascript style. We only run this once per change but it's good to have multiple lint-enabled hosts in case one is down.
-Install the gjslint checker by following the relevant instructions here:
+Install the gjslint checker by following the relevant instructions here (you man need to install python-setuptools to get easy_install on Debian/Ubuntu):
 https://developers.google.com/closure/utilities/docs/linter_howto
@@ Line 344: / Line 344: @@
 <pre>
-apt-get install libunwind7-dev
+sudo apt-get install libunwind8-dev
 </pre>
@@ Line 351: / Line 351: @@
 <pre>
 wget ....
-tar -zxf gperftools-2.0.tar.gz
+tar -zxf gperftools-2.1.tar.gz
-cd gperftools-2.0
+cd gperftools-2.1
 ./configure
 make

@@ Line 328: / Line 328: @@
 </pre>
-Finally drop Simon an email asking him to enable C++ lint for your slave.
+Finally let Simon or Peter know, or raise an issue, asking them to enable C++ lint for your slave.
 == Enabling the Javascript Lint Checker ==
@@ Line 337: / Line 337: @@
 https://developers.google.com/closure/utilities/docs/linter_howto
-Finally drop Simon an email asking him to enable Javascript lint for your slave.
+Finally let Simon or Peter know, or raise an issue, asking them to enable Javascript lint for your slave.
 == Enabling the heap checker ==
@@ Line 358: / Line 358: @@
 sudo ldconfig
 </pre>
+Finally let Simon or Peter know, or raise an issue, asking them to enable the heap checker for your slave.

@@ Line 48: / Line 48: @@
 === Slave Configuration ===
-Create the slave:
+Create the slave (the package creates the buildbot user automatically for you):
 <pre>

@@ Line 204: / Line 204: @@
 === Build Slave Installation ===
 As root:
-RenZO to confirm...
+<pre>
 === Slave Configuration ===