ReleaseEngineering/Applications: Difference between revisions

removing obsolete applications
mNo edit summary
(removing obsolete applications)
 
(33 intermediate revisions by 10 users not shown)
Line 1: Line 1:
= RelEng App Store =
This page is an incomplete attempt to categorize all of the applications (or systems, or infrastructures, or whatever you'd like to call them) installed and in use by release engineering.
== build masters ==
we have lots!


canonical list is supposed to be http://hg.mozilla.org/build/tools/raw-file/default/buildfarm/maintenance/production-masters.json
= App Store =
* [[ReleaseEngineering/Applications/Ship It]]
* [[ReleaseEngineering/Applications/Tooltool]]
* [[ReleaseEngineering/Applications/RelengAPI]]
* [[Balrog]]


source for buildbot is at http://hg.mozilla.org/build/buildbot/
= What the heck? =
We're not quite sure yet what these pages should contain.  Here are some questions that should be answered for each application:


== clobberer ==
== Deployment Questions ==
https://build.mozilla.org/clobberer/ and https://build.mozilla.org/stage-clobberer
 
Source is at http://hg.mozilla.org/build/tools/file/default/clobberer
 
DB is a sqlite file local to the web server
 
== buildapi ==
includes self-serve, wait time reports, pending/running
everything under https://build.mozilla.org/buildapi
 
source is at http://hg.mozilla.org/build/buildapi
 
staging and production instances are running on cruncher, proxied by build.m.o
 
uses two mysql slave databases hosted by IT
 
uses a memcached daemon running on cruncher
 
uses a rabbitmq daemon running on cruncher
 
== slavealloc ==
 
== regression detection ==
code is http://hg.mozilla.org/graphs/file/9c02347596b4/server/analysis
 
runs on cruncher via cronjob under catlee's account from ~/graphs/server/analysis
 
=deployment questions=
* what languages are needed and their version
* what languages are needed and their version
** if python, what python modules - can they be run in a virtualenv
** if python, what python modules - can they be run in a virtualenv
Line 42: Line 17:
* what is the command line parameters to start the web service
* what is the command line parameters to start the web service
* does it have any special configuration or init files
* does it have any special configuration or init files
** How are those backed up?
* does it require root or sudo
* does it require root or sudo
* does it require a special directory layout
* does it require a special directory layout
* will it generate/use temp files or non-database assets?
* will it generate/use temp files or non-database assets?
** which of those need to be backed up?
** how is that done?
* what version of mysql and what database config, where is the sql to init the tables
* what version of mysql and what database config, where is the sql to init the tables
** what is the backup strategy?
* does memcached have a min/max memory? which processes read/write to it - can it be on different IP
* does memcached have a min/max memory? which processes read/write to it - can it be on different IP
* what ports will be opened for listening
* what ports will be opened for listening
* cronjobs that need to be run
* cronjobs that need to be run
* if outside services are utilized, what is that list
* if outside services are utilized, what is that list
== Maintenance Questions ==
* what are common issues we run into, and how to debug?
** place in buildduty docs?
* where is the code/schema for hacking/reading?
* are there special passwords/accounts/acl's, and what are they? (not in public docs)
Confirmed users
2,456

edits