* Run buildbot on the slave system, preferably by starting it automatically when your system boots. It should be running with the buildbot user ID.
You may also want to set up ccache to work with buildbot (strongly recommended to speed up builds). If you create a directory ~/buildbot/bin, it will be added to the execution PATH when buildbot runs commands on the slave. This directory can have symbolic links like the following:
<pre>lrwxrwxrwx 1 buildbot buildbot 15 Aug 26 11:39 gcc -> /usr/bin/ccachelrwxrwxrwx 1 buildbot buildbot 15 Aug 26 11:40 cc -> /usr/bin/ccachelrwxrwxrwx 1 buildbot buildbot 15 Aug 26 11:40 c++ -> /usr/bin/ccachelrwxrwxrwx 1 buildbot buildbot 15 Aug 31 23:46 gfortran -> /usr/bin/ccache </pre>
They should point to the actual location of ccache if it is not in /usr/bin.
Your system may be behind a firewall. It does not have to have a distinct public IP address.
== Sample Slave Configuration File ==
You must edit the settings for basedir, slavename, and password. The basedir should be the absolute and fully expanded name of the directory containing the configuration file. For example, if the home directory for the buildbot user is /var/lib/buildbot and your slavename is set to 'debian-x86_64' , then basedir might be
'/var/lib/buildbot/slaves/debian-x86_64 '. The password should not be anything valuable. You'll be asked to provide the slavename and password so that they may be added to the master configuration on buildbot.octave.org. Do '''not''' post the password to the octave-maintainers mailing list.
== Space Requirements ==
Building Octave takes a significant amount of disk space. With debugging symbols, you may need several GB for each build, plus room for ccache (possibly 50GB) if you use it. If you use a cache size that is larger than the default, you'll need to specify that in the .ccache/ccache.conf file using a line like
<pre>max_size = 50G </pre>
If the directory containing the build and ccache directories doesn't have sufficient space, then these directory names may point to a separate partition that does have enough space available.
== Starting the Slave ==
With everything in place, you can run the slave server with the following commands (assuming that your basedir is
<pre>cd ~buildbot/slavessudo -u buildbot buildslave start debian-x86_64 </pre>
If successful, buildbot will respond with <pre> ... FIXME ... </pre> [[Category: Development]]