ReferencePlatforms: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 4: Line 4:
|-
|-
! Platform  
! Platform  
! Build ref page  
! Build ref page
! Machine name
! Testing ref page  
! Testing ref page  
! Machine name
|-
|-
| Windows 32-bit  
| Windows 32-bit  

Revision as of 19:11, 30 September 2010

Build Reference Platforms

Platform Build ref page Testing ref page
Windows 32-bit Win32 (win32-ix-ref & win2k3sp2-ref-vm) WinXP & Win7 32-bit (talos-r3-xp-ref, talos-r3-w7-ref)
Windows 64-bit Win64 (win64-ix-ref) Win7 64-bit (t-r3-w764-ref)
Mac OS X 10.5 MacOSX 10.5 (bm-mini-build-ref) Leopard (talos-r3-leopard-ref)
Mac OS X 10.6 MacOSX 10.6 (moz2-darwin10-ref) Snow Leopard (talos-r3-snow-ref)
Linux 32-bit CentOS 5.0 (CentOS-5.0-ref-tools-vm linux-ix-ref) Fedora 12 (talos-r3-fed-ref)
Linux 64-bit CentOS 5.0 64-bit (linux64-ref-platform) Fedora 12 x64 (talos-r3-fed64-ref)
Maemo CentOS 5.0 Nokia N810 & Nokia N900
Android CentOS 5.0 -tbd-

Refreshing the ref machines before asking IT to refresh their image

When we update 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

Once we know that the ref machines (from the previous section) are up-to-date we need to ask IT to refresh their images.

If the change only affects builders tell IT to refresh the image of the builders (discard the VMs from the list) and if the change affects testers only choose from the testing ref machines.

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