ReleaseEngineering/How To/Setup a buildbot master: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(deleting obsolete page)
 
(44 intermediate revisions by 11 users not shown)
Line 1: Line 1:
This page describes how to set-up a new Buildbot Master.


= Hardware =
== Production masters ==
* Current policy is one buildbot master instance per VM
* 64-bit guest
* 2 virtual CPUs
* 6 GB RAM
* 6 GB swap
* 20GB root partition
== OS ==
* Install CentOS 5.5
* Install puppet
** Configure to point to master-puppet1.build.mozilla.org
= The Master Instance =
First, to get the master directory prepped and cronjobs set-up, do this on the machine:
<pre>
# cltbld@wherever
BASEDIR=/builds/buildbot/my_master
MASTER_NAME=my_master_name # Must be one from ./setup-master.py -8 -l
PYTHON=/tools/python-2.6.5/bin/python
VIRTUALENV=/tools/python-2.6.5/bin/virtualenv
HG=/tools/python-2.6.5/bin/hg
hg clone http://hg.mozilla.org/build/buildbot-configs
cd buildbot-configs
make -f Makefile.setup all BASEDIR=$BASEDIR MASTER_NAME=$MASTER_NAME VIRTUALENV=$VIRTUALENV PYTHON=$PYTHON HG=$HG
</pre>
Then, update whatever files the Makefile instructs you too with correct passwords, descriptions, etc.
= Support files, Wikis =
Update [http://hg.mozilla.org/build/tools/file/default/buildfarm/maintenance/production-masters.json production-masters.json] in tools and the [https://intranet.mozilla.org/RelEngWiki/index.php/Masters master list], if appropriate
= IT-related things =
* Nagios
** PING
** Swap
** avg load
** buildbot
** disk - /
** disk - /builds
* Mysql access to the DB server
* Add master to Tinderbox whitelist
= SSH Keys =
* Copy production ssh keys (for ffxbld and trybld) to ~/.ssh.
* Make sure you can ssh to ffxbld@dm-pvtbuild01.mozilla.org and ffxbld@stage.mozilla.org
= Other =
* Make sure NTP is running!

Latest revision as of 21:46, 19 November 2018