ReferencePlatforms: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 1: Line 1:
= Build Reference Platforms  =
= Build Reference Platforms  =


{| border="1px" class="sortable" style="border: 1px solid black;"
{| border="1px" style="border: 1px solid black;" class="sortable"
|-
|-
! Platform  
! Platform  
! Build ref page 
! Build ref  
! Testing ref page
! Hostname
! Testing ref  
! Hostname
|-
|-
| Windows 32-bit
| Win32
| [[ReferencePlatforms/Win32|Win32]] - win32-ix-ref
| [[ReferencePlatforms/Win32|Win32]]  
| [[ReferencePlatforms/Test/WinXP|WinXP]] & [[ReferencePlatforms/Test/Win7|Win7 32-bit]] - talos-r3-{xp|w7}-ref
| win32-ix-ref  
| [[ReferencePlatforms/Test/WinXP|WinXP]] & [[ReferencePlatforms/Test/Win7|Win7 32-bit]]  
| talos-r3-{xp|w7}-ref
|-
|-
| Windows 64-bit
| Win64
| [[ReferencePlatforms/Win64|Win64]] - win64-ix-ref
| [[ReferencePlatforms/Win64|Win64]]  
| [[ReferencePlatforms/Test/Win7 64-bit|Win7 64-bit]] - t-r3-w764-ref
| win64-ix-ref  
| [[ReferencePlatforms/Test/Win7 64-bit|Win7 64-bit]]  
| t-r3-w764-ref
|-
|-
| Mac OS X 10.5  
| OS X 10.5  
| [[ReferencePlatforms/Mac-10.5|MacOSX 10.5]] - bm-mini-build-ref
| [[ReferencePlatforms/Mac-10.5|MacOSX 10.5]]  
| [[ReferencePlatforms/Test/Leopard|Leopard]] - talos-r3-leopard-ref
| bm-mini-build-ref  
| [[ReferencePlatforms/Test/Leopard|Leopard]]  
| talos-r3-leopard-ref
|-
|-
| Mac OS X 10.6  
| OS X 10.6  
| [[ReferencePlatforms/Mac-10.6|MacOSX 10.6]] - moz2-darwin10-ref
| [[ReferencePlatforms/Mac-10.6|MacOSX 10.6]]  
| [[ReferencePlatforms/Test/SnowLeopard|Snow Leopard]] - talos-r3-snow-ref
| moz2-darwin10-ref  
| [[ReferencePlatforms/Test/SnowLeopard|Snow Leopard]]  
| talos-r3-snow-ref
|-
|-
| Linux 32-bit
| Linux 32  
| [[ReferencePlatforms/Linux-CentOS-5.0|CentOS 5.0]] - linux-ix-ref
| [[ReferencePlatforms/Linux-CentOS-5.0|CentOS 5.0]]  
| [[ReferencePlatforms/Test/FedoraLinux|Fedora 12]] - talos-r3-fed-ref
| linux-ix-ref  
| [[ReferencePlatforms/Test/FedoraLinux|Fedora 12]]  
| talos-r3-fed-ref
|-
|-
| Linux 64-bit
| Linux 64  
| [[ReferencePlatforms/Linux-CentOS-5.0 64-bit|CentOS 5.0 64-bit]] - linux64-ref-platform
| [[ReferencePlatforms/Linux-CentOS-5.0 64-bit|CentOS 5.0x64]]  
| [[ReferencePlatforms/Test/FedoraLinux64|Fedora 12 x64]] - talos-r3-fed64-ref
| linux64-ref-platform  
| [[ReferencePlatforms/Test/FedoraLinux64|Fedora 12 x64]]  
| talos-r3-fed64-ref
|-
|-
| Maemo  
| Maemo  
| [[ReferencePlatforms/Linux-CentOS-5.0|CentOS 5.0]]  
| [[ReferencePlatforms/Linux-CentOS-5.0|CentOS 5.0]]  
| [[ReferencePlatforms/Test/Maemo|Nokia N810]] & [[ReferencePlatforms/Test/N900-PR1.2|Nokia N900]]  
|  
| Nokia [[ReferencePlatforms/Test/Maemo|N810]] / [[ReferencePlatforms/Test/N900-PR1.2|N900]]  
|
|-
|-
| Android  
| Android  
| [[ReferencePlatforms/Linux-CentOS-5.0|CentOS 5.0]]  
| [[ReferencePlatforms/Linux-CentOS-5.0|CentOS 5.0]]  
|
| -tbd-  
| -tbd-  
|
|}
|}


* 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  ==
== Refreshing the ref machines before asking IT to refresh their image  ==
Line 46: Line 64:
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'''  
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'''  


Once we know that the ref machines (from the previous section) are up-to-date we need to ask IT to refresh their images.
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 refreshing the VMs listed as desupported on previous section) and if the change affects testers only choose from the testing ref machines.
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.  


== Newly cloned mini setup notes  ==
== Newly cloned mini setup notes  ==
Line 54: Line 72:
{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.  
{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 ==
== Staging machines ==
* The ref platforms are pointing to production masters (OPSI and puppet)
 
* Change the following on them
*The ref platforms are pointing to production masters (OPSI and puppet)  
** TODO add link
*Change the following on them  
**TODO add link


= Geriatric Machines  =
= Geriatric Machines  =

Revision as of 19:39, 30 September 2010

Build 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

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 refreshing the VMs listed as desupported on previous section) 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