Buildbot/IT Mozilla2 Support Document
From MozillaWiki
< Buildbot
Machines
Mozilla2 Waterfall
Mozilla2 Buildslave list
All of following machines live in the build network. This makes their FQDN $name.build.mozilla.org.
Name | Platform | Tree | Support Tier* |
production-master (master) | linux | N/A | X |
moz2-linux-slave1 moz2-linux-slave02 moz2-linux-slave03 |
linux | Mozilla2 Actionmonkey | X |
moz2-win32-slave1 moz2-win32-slave02 moz2-win32-slave03 |
win32 | Mozilla2 Actionmonkey | X |
bm-xserve16 bm-xserve17 bm-xserve18 |
Mac OS X 10.5 | Mozilla2 Actionmonkey | X |
- * - tiers explained
Fixing failing builds
Clobber the failing slave and force a new build. (Note: forcing a new build will not necessarily cause a build on the failing slave. This is OK.)
- Find the hostname in the Tinderbox log (look for 'Building on: XXX' where 'XXX' is a hostname)
- Login to the slave using provided credentials (SSH for Linux, RDP for Windows, VNC for Mac).
- On Windows, kill any ssh/sh/make/other unix-type processes in the task manager.
- Go to the builder directory (e:\builds\moz2_slave\$builder_name on win32, /builds/moz2_slave/$builder_name on linux/mac [where $builder_name matches the name of the failing build on Tinderbox])
- Delete the subdirectory named 'build'.
- Force a new build
- Click on the appropriate column title on the Waterfall (eg. 'mozilla-central-win32')
- Fill out the Force Build form. 'Branch to build' MUST be specified (branch name is part of the builders name. eg, mozilla-central or actionmonkey).
- Click 'Force Build'.
- If the next build doesn't go green, contact RelEng.
Builds not happening at all
Make sure all slaves are connected (Note: do NOT use the 'Ping Builder' button on the Waterfall, it will break future builds):
- Go to the Buildslave List page.
- For any slaves that are listed as 'NOT connected' we need to connect the slave:
- Login to the slave using provided credentials (SSH for Linux, RDP for Windows, VNC for Mac).
- For Windows:
- Kill any ssh/sh/make/other unix-type processes in the task manager.
- If there is not an existing MSYS window start one with the desktop icon.
- Start Buildbot with '/d/mozilla-build/python25/scripts/buildbot start /e/builds/moz2_slave'.
- Minimize the MSYS window
- For Mac:
- Start Terminal if not already running.
- Start Buildbot with 'buildbot start /builds/moz2_slave'
- Minimize the Terminal window (do NOT close it).
- For Linux:
- Start Buildbot with 'buildbot start /builds/moz2_slave'.
- Wait 30 seconds and check the Buildslave List page again. If slaves still aren't connected contact RelEng.
It is almost always a bad idea to reboot the buildmaster VM. It runs multiple Buildbot masters. Unless it is completely unreachable please do not restart this machine without talking to someone from RelEng first.