Fuego jobs (or test run instances) are located in
/home/jenkins/fuego/jobs/<test_name>/builds.

This directory has the following items:
 * a directory for each build
   * the directory name is a timestamp in the format: YYYY-MM-DD_HH-mm-ss
   * each build directory has the files:
     * build.xml
     * changelog.xml
     * log
 * a symlink to each build directory, using the build number
   * example: 3 -> 2016-08-02_12-52-13
 * last.* files (5 of them)
   * lastFailedBuild, lastStableBuild, lastSuccessfulBuild, lastUnstableBuild, lastUncessfulBuild
   * each of this is a symlink to the last build of the indicated type

In the top directory (/home/jenkins/fuego/jobs/<test_name>), you can find:
 * nextBuildNumber = ascii number for the next build number to use
 * config.xml = jenkins attributes for this test
 * lastStable = symlink to builds/lastStableBuild
 * lastSuccessful = symlink to builds/lastSuccessfulBuild

= how to make your own job instance =
Here are some steps to make your own job instance. (I documented this 
for my work on ftc).
 * read nextBuildNumber
 * write nextBuildNumber with build_num+1
 * generate timestamp
 * create timestamp directory in builds
   * ex: builds/2016-07-31_12-00-00
 * generate build.xml, changelog.xml log
   * maybe by copying a previous build
 * change <number>
 * change <startTime>
   * you can use timetamp from:
      * python time.mktime((2016,7,31,12,0,0,-1,-1,-1))) * 1000
 * create build_num symlink to timestamp dir
   * ln -s 3 2016-07-31_12-00-00

 * unlink lastStableBuild and symlink 3 to lastStableBuild
 * unlink lastSuccessfulBuild and symlink 3 to lastSuccessfulBuild
 * need to set permissions to (jenkins, nogroup) on all newly create file
 * tell jenkins to reload configuration
   * using 'jcmd reload-configuration'