ReferencePlatforms/Linux-CentOS-5.0: Difference between revisions

 
(7 intermediate revisions by 5 users not shown)
Line 11: Line 11:
  0c3990be2271bf44c1495aa0003b5552  CentOS-5.0-i386-bin-5of6.iso
  0c3990be2271bf44c1495aa0003b5552  CentOS-5.0-i386-bin-5of6.iso
  9e6f91a5292f46b02777133765fc03fe  CentOS-5.0-i386-bin-6of6.iso
  9e6f91a5292f46b02777133765fc03fe  CentOS-5.0-i386-bin-6of6.iso
TB: Thunderbird build clients use a separate /buildbot partition of 80GB.  Now that we reboot after each build, be sure to "tune2fs -c 0" the buildbot partition to avoid an fsck of it every 20 reboots.


=== Package Selection ===
=== Package Selection ===
Line 24: Line 26:
* '''Applications'''
* '''Applications'''
** Editors
** Editors
** Test-based internet
** Text-based internet
*** Add lynx
*** Add lynx
* '''Development'''
* '''Development'''
Line 104: Line 106:
  make install 2>&1 | tee /tools/dist/logs/python2.5.1-make_install.log
  make install 2>&1 | tee /tools/dist/logs/python2.5.1-make_install.log
  cd /tools/
  cd /tools/
  ln -s python2.5.1 python
  ln -s python-2.5.1 python


== Version 3 ==
== Version 3 ==
Line 527: Line 529:
==== Install EPEL ====
==== Install EPEL ====
As root,
As root,
  rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm
  rpm -Uvh http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm


==== Move the JDK ====
==== Move the JDK ====
Line 661: Line 663:
The buildbot.tac file will automatically be generated to send the slave to the correct staging master (staging-master or sm-staging-try-master).
The buildbot.tac file will automatically be generated to send the slave to the correct staging master (staging-master or sm-staging-try-master).


== switchover from staging to production ==
===Run the slave through staging===
* add slaves to [http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla2/config.py buildbot-configs/mozilla2/config.py], get review, land, update masters
see [[ReleaseEngineering:BuildSlaveSetup]]
* stop slave process
* switchover the .ssh keys to use production keys
* manually ssh to the production machines listed below and enter "yes" to the question about accepting the machine signature
# production
ssh -i ~/.ssh/ffxbld_dsa ffxbld@aus2-staging.mozilla.org
ssh -i ~/.ssh/ffxbld_dsa ffxbld@dm-symbolpush01.mozilla.org
ssh -i ~/.ssh/ffxbld_dsa ffxbld@stage.mozilla.org
ssh -i ~/.ssh/ffxbld_dsa ffxbld@stage-old.mozilla.org
ssh -i ~/.ssh/ffxbld_dsa ffxbld@hg.mozilla.org
ssh -i ~/.ssh/ffxbld_dsa ffxbld@cvs.mozilla.org
* edit /builds/slave/buildbot.tac to change "staging-master" to "production-master" or "production-master02".
* clobber all build trees on slave
* start slave process
Confirmed users
3,104

edits