(added note to tweak default gcc search paths) |
(→Setup) |
||
Line 10: | Line 10: | ||
# [http://ronaldbradford.com/blog/installing-buildbot-2008-07-28/ Install Buildbot] |
# [http://ronaldbradford.com/blog/installing-buildbot-2008-07-28/ Install Buildbot] |
||
# Install [[Bazaar]] (used to obtain LaunchPad sourcs) |
# Install [[Bazaar]] (used to obtain LaunchPad sourcs) |
||
+ | # Make sure that all [[Compiling#Package_Dependencies|build dependencies]] are met |
||
# Send an email to '''drizzlebuild @ 42sql dot com''' with the following information |
# Send an email to '''drizzlebuild @ 42sql dot com''' with the following information |
||
#* Name (e.g. Joe Bloggs) |
#* Name (e.g. Joe Bloggs) |
Revision as of 13:57, 13 August 2008
Overview
The success of Drizzle will be due to the contributions of the community. You don't have to be a coder to contribute, there are many other areas including testing, documentation and contributing to the build process for example.
Contributing a buildbot slave will help drizzle developers test across a various number of configurations.
Setup
To run a buildbot slave, you need to do.
- Install Buildbot
- Install Bazaar (used to obtain LaunchPad sourcs)
- Make sure that all build dependencies are met
- Send an email to drizzlebuild @ 42sql dot com with the following information
- Name (e.g. Joe Bloggs)
- OS - Name, Version & Architecture ( CentOS 5 64bit)
- uname -a
- When you get a response, you will receive a build slave name (e.g. centos5_64) and a password (e.g. PaSSw0rd)
- Follow the following slave instructions.
# # Create separate user # # Recommended but not required to create a separate user # su - useradd buildbot su - buildbot # # Create Slave # buildbot create-slave /home/buildbot/slave drizzlebuild.42sql.com:9989 [slavename] [password] cd /home/buildbot/slave/info echo "Put Your Name Here < and some cryptic email text> ” > admin echo “Drizzle - Name Version & Architecture “`uname -a` > host cat admin host # # e.g. "Ronald Bradford < ronald.bradford @ Google Mail >" # e.g. "Drizzle - CentOS 5 64bit - # # # Start Slave # # cd /home/buildbot/slave buildbot start /home/buildbot/slave > start.log tail -f /home/buildbot/slave/twistd.log
If all working you will be getting output immediately, as well as seeing a status at Drizzle Build Slaves
Full details at Building sources with BuildBot
Setting search paths
If your buildbot fails in configure because it cannot find your installation of library dependencies, consider setting the default environment of your buildbot user.
For GCC you can set CPATH and LIBRARY_PATH to add more directories to the default include and library search paths.
This allows you to install e.g. libevent in a non-standard place and still be able to become a buildbot slave without cluttering your standard paths.