From MozillaWiki
Jump to: navigation, search
Do not edit this page THIS PAGE IS PROPOSED FOR DELETION 2018-08-06
Buildbot is being retired in bug 1488913 and all relevant Talos content has been moved to TestEngineering/Performance/Talos.


[Addon On Demand Performance Testing Buildbot Waterfall]

[AddonTester Tinderbox Waterfall]

Network Flow

  • test request is generated by AMO and pushed into the system via the trigger.cgi script
  • addon buildbot master schedules the AMO test request to the appropriate talos slaves
  • talos slave picks up test request, tests
  • talos slave pushes results to the production graph server
  • production graph server packages the results and pushes them directly into the production AMO db
  • talos results are reported to the tinderbox waterfall ([AddonTester Waterfall])

Setup Details




Update Production Master

This would be a standard update/reconfig for code changes in buildbotcustom/buildbot-configs.

cd /builds/buildbot/production-addons
cd buildbot-configs
hg pull -u
cd ..
cd buildbotcustom
hg pull -u
cd ..
make reconfig

Generate New Production Master From Scratch

If updating the production master is unsuccessful, then you can start from scratch.

cd /builds/buildbot/production-addons
make stop
cd ..
mv production-addons/master/ .
rm -rf production-addons
cd buildbot-configs
hg pull -u
make -f Makefile.setup MASTER_NAME=production-addon_master BASEDIR=/builds/buildbot/production-addons PYTHON=/usr/bin/python2.6 VIRTUALENV=/usr/bin/virtualenv-2.6 BUILDBOTCUSTOM_BRANCH=default BUILDBOTCONFIGS_BRANCH=default virtualenv deps install-buildbot master master-makefile
cd ..
mv production-addons/master/.
cd production-addons
make start

Finish by rebooting the addon talos slaves to force them to connect to the new master

Slave Maintenance
  • slaves should reconnect on reboot
  • if changes are made to the production talos slaves managed by releng then the changes will have to be manually rolled out to the addon slave, as they are outside the releng vpn

Trigger Script


Causes individual addon tests to be pushed into the system. Uses the local apache server.



  • restart apache
  • check file permissions

Manual Changes to Slaves

In order to support the AMO API, we need to use python 2.6 and oauth2. This is done by installing python 2.6 (alos adjusting the environment path from c:\python24 to c:\python26), then doing:

#NOTE: this requires a GUI to run
#Now open a new command window (or ssh session)
easy_install pywin32-216.win32-py2.6.exe oauth2 pyyaml

For osx, we need:

# adjust to python2.6
cd ~/bin
rm python
rm python-config
ln -s /usr/bin/python2.6 python
ln -s /usr/bin/python2.6-config python-config
easy_install oauth2 

For linux, we need to:

#adjust to python2.6
cd ~/bin
rm python
rm python-config
ln -s /usr/bin/python2.6 python
ln -s /usr/bin/python2.6-config python-config
#get modules httplib2, oauth2
#install modules via 'python install'