Lieven Govaerts wrote:
> On Sat, Nov 14, 2009 at 1:40 AM, Julian Foad <julian.foad_at_wandisco.com> wrote:
>> Lieven Govaerts wrote:
>>> Indeed, in the buildslave basedir info/host and info/admin files. See
>>> step 8 in the manual:
>> Ah, the manual! That was what I needed. Thanks, Lieven.
>> I have run the appropriate "buildbot create-slave" command and edited
>> the info files. Dave is taking over now. He has to install a few more
>> buildbot dependencies, I think, before it will run properly, as well as
>> figure out how to tell it how to find and run our "svnbuild.sh" etc.
>> scripts, and make it actually connect to your machine (if it isn't
>> already trying). I passed Dave the connection info that you emailed me.
> I've restarted the buildbot master, it's now ready to accept your build slave.
> If you start up the slave with the info I've sent you, it will connect
> to the master. On the first connection it will automatically create a
> new directory x64-centos in the base directory.
> The working copy will be put in the BASEDIR/x64-centos/build
> directory, which is considered as cwd. So if you put the scripts in
> BASEDIR/x64-centos, the master will find them there.
The CentOS bot is alive and kicking. It's running davautocheck for the
core tests, and javaHL, python-swig, and perl binding tests. Some
python libraries had to be installed manually, since CentOS packages
don't deliver everything, but they're listed in the info/host file.
The ruby tests are omitted on this bot right now. They get a couple of
failures, then a SEGV about halfway through on this line that I'm trying
to figure out:
Ruby's OK on x64-ubuntu, so it's a CentOS issue.
Lieven, unless you see anything wrong, you can make it fully live at
Received on 2009-11-15 02:12:24 CET