ReferencePlatforms: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 60: Line 60:
*To stop supporting at some point win2k3sp2-ref-vm & CentOS-5.0-ref-tools-vm
*To stop supporting at some point win2k3sp2-ref-vm & CentOS-5.0-ref-tools-vm


== Refreshing the ref machines before asking IT to refresh their image  ==
== Tracking ref images being refreshed ==
Every time we do a relevant change to [http://hg.mozilla.org/build/tools/log/tip/buildbot-helpers/buildbot-tac.py buildbot-tac.py] we have to update the '''build-tools''' repo on the ref images (through puppet on linux/darwin builders and manually on all others) and then ask IT to refresh the images (either builders or testers).


When we update buildbot-tac.py ([http://hg.mozilla.org/build/tools/log/4b41e311f539/buildbot-helpers/buildbot-tac.py this view] shows you last time we have done a change) on the tools repo we have to generate a new build-tools RPM for Linux and Darwin slaves and download the tools zip unto the Windows ref machines. '''TODO add link to steps to do this'''
NOTE: Do not ask to refresh the linux/windows ref VMs.


Once we know that the ref machines (from the previous section) are up-to-date we need to ask IT to refresh their images.  
Please keep track of when we ask IT to refresh the images.
* refresh requested for [https://bugzilla.mozilla.org/show_bug.cgi?id=600971#c0 talos-ref-leopard-ref] and [https://bugzilla.mozilla.org/show_bug.cgi?id=601151#c0 talos-ref-snow-ref] to [http://hg.mozilla.org/build/tools/rev/bb8b3a7c86ac buildbot-tac.py's] latest revision (bb8b3a7c86ac).


If the change only affects builders tell IT to refresh the image of the builders (discard refreshing the VMs listed as desupported on previous section) and if the change affects testers only choose from the testing ref machines.  
NOTE: Filed {{bug|601172}} to not require asking IT to refresh the images for buildbot-tac.py changes


== Newly cloned mini setup notes  ==
== Newly cloned mini setup notes  ==

Revision as of 17:31, 1 October 2010

Reference Platforms

Platform Build ref Hostname Testing ref Hostname
Win32 Win32 win32-ix-ref WinXP & Win7 32-bit talos-r3-{xp|w7}-ref
Win64 Win64 win64-ix-ref Win7 64-bit t-r3-w764-ref
OS X 10.5 MacOSX 10.5 bm-mini-build-ref Leopard talos-r3-leopard-ref
OS X 10.6 MacOSX 10.6 moz2-darwin10-ref Snow Leopard talos-r3-snow-ref
Linux 32 CentOS 5.0 linux-ix-ref Fedora 12 talos-r3-fed-ref
Linux 64 CentOS 5.0x64 linux64-ref-platform Fedora 12 x64 talos-r3-fed64-ref
Maemo CentOS 5.0 Nokia N810 / N900
Android CentOS 5.0 -tbd-
  • To stop supporting at some point win2k3sp2-ref-vm & CentOS-5.0-ref-tools-vm

Tracking ref images being refreshed

Every time we do a relevant change to buildbot-tac.py we have to update the build-tools repo on the ref images (through puppet on linux/darwin builders and manually on all others) and then ask IT to refresh the images (either builders or testers).

NOTE: Do not ask to refresh the linux/windows ref VMs.

Please keep track of when we ask IT to refresh the images.

NOTE: Filed bug 601172 to not require asking IT to refresh the images for buildbot-tac.py changes

Newly cloned mini setup notes

{fed,fed64,leopard,snow,xp} test machines come up into the production pool after cloning, with no additional steps required (make sure you have updated graphserver, and checked in patches for opsi, puppet, graphserver, and build configs for the masters). If a fed{32,64} or mac box doesn't come online, check PostImage for setting hostname. Win7 32-bit currently doesn't have OPSI and needs the buildbot.tac file to be edited manually and a reboot.

Staging machines

  • The ref platforms are pointing to production masters (OPSI and puppet)
  • Change the following on them
    • TODO add link

Geriatric Machines

  • XP - Non-SSE2 Testing
  • Fedora - Non-SSE2 Testing
  • 10.5 - PPC Testing
  • 10.5-Xserve - PPC Testing using Xserve build reference image

Other Build/Release Infrastructure


Mobile Specific Infrastructure

Post Image procedure

The steps to take after cloning a system can be found here.

The steps to run a slave through staging then put it into production can be found at ReleaseEngineering:BuildSlaveSetup

Historical/Other