ReleaseEngineering/Preproduction/Masters: Difference between revisions

deleting obsolete page
mNo edit summary
(deleting obsolete page)
 
Line 1: Line 1:
At the moment all preproduction masters run on '''preproduction-master.build.mozilla.org''' server.


Pre-production system has a "managing" master, which runs quality check of the releng repositories.
At the moment the managing master runs at [http://preproduction-master.build.mozilla.org:8710 http://preproduction-master.build.mozilla.org:8710] and the corresponding repository is [http://hg.mozilla.org/build/preproduction/ here].
This master runs the following check for each push:
* sets up a virtual environment and installs all needed modules
* runs [http://hg.mozilla.org/build/buildbot-configs/file/tip/test-masters.sh test-masters.sh]
* runs pylint
* generates a coverage report for buildbotcustom and publishes it at [http://preproduction-stage.build.mozilla.org/coverage/buildbotcustom/ http://preproduction-stage.build.mozilla.org/coverage/buildbotcustom/]
There are 5 other types of masters running on the same machine:
* scheduler master
** polls Firefox hg repositories with reduced poll interval (6h)
** uses local MySQL database as a backend
* tests scheduler master
* [http://preproduction-master.build.mozilla.org:8010/ builder master]
* [http://preproduction-master.build.mozilla.org:8012/ tests master]
* [http://preproduction-master.build.mozilla.org:8020/ release master]
Once a week the managing master recreates virtual environment for all masters listed above, removes all database entries and restarts the servers.
There is a hourly cronjob which scans twistd.log files for unhandled exceptions and emails them to release@ mailing list.
Confirmed users
2,456

edits