Tinderbox Setup notes

Setting up a tinderbox for Chandler is documented here.

Requirements

• First make sure you can build Chandler: BuildingChandlerDesktop

• Special additional requirements on Windows:
  • You need to be in Cygwin shell for the Tinderbox client scripts to work (?).
  • Extra Cygwin packages/programs needed: scp, tar, gzip, zip, gettext, gettext-dev. Also rsync if you plan to upload anything.
  • Download the NSIS program and install it. Make sure the installation directory appears in your path after installing. You can download it from http://nsis.sourceforge.net - we are currently using version 2.02. The README.txt at internal/installers/win/ outlines in detail what needs to be done and also includes instructions on how to build the windows installer under linux.

• Special setup for Linux:
  • You need to prepare your RPM environment:
    • cd ~
    • mkdir rpm
    • mkdir rpm/BUILD
    • mkdir rpm/SOURCES
    • mkdir rpm/SPECS
    • mkdir rpm/SRPMS
    • mkdir rpm/RPMS
    • mkdir rpm/RPMS/i386
    • create a ~/.rpmmacros file that contains the following:
      • %_topdir /home/whatever_user_name_where_rpm_lives/rpm

• Special setup for Macs:
  • System Preferences > Keyboard & Mouse > Full keyboard access: set to "All controls" (needed if you run recorded scripts)

Performance boxes

• start the tests using the command './cycle.py' described in setup

Setup

• Tinderbox builds are preset to use the directory ~/tinderbuild for all working files.
  • this is automatically created for you
  • output directory where build results get published locally can be specified at start time, but defaults to ~/output
• in your home directory, issue the commands:
  • svn co http://svn.osafoundation.org/tools/hardhat
  • cd hardhat
  • ./cycle.py --help - This will display input options for the control script
    • Note: cycle.py calls tinderbox.py to do the real work. If you just want to run one cycle for test purposes, use tinderbox.py instead of cycle.py

• For people outside OSAF: you need to pass in option -s (--skipRsync).

• Naming your tinderbox
  • tinderbox builds are distinguished by a unique identifier
  • the name is usually of the form <machine-id>-<OS-id>
    • example: hilo-win

• After determining your name, confirm other options (defaults are usually OK)
• Start your tinderbox (you should already be in the ~/hardhat directory)
  • ./cycle.py --skipRsync -a <your-name@your-domain> <your-build-id>
  • monitor your terminal window to confirm there are no startup errors
    • build directory and results directory are created for you
    • build status email goes to the tinderbox server
    • build alert email goes to your "-a | --alert" email address
• monitor the tinderbox server page (http://builds.osafoundation.org/tinderbox/Chandler/status.html) to confirm that your build is being displayed.

• If you want to do manual Tinderbox testing without uploading anything or reporting build status:
  • ./tinderbox.py -s -a <your email> <build name for your tbox>