ReleaseEngineering/Applications: Difference between revisions
Line 55: | Line 55: | ||
** place in buildduty docs? | ** place in buildduty docs? | ||
* where is the code/schema for hacking/reading? | * where is the code/schema for hacking/reading? | ||
* are there special passwords/accounts/acl's, and what are they? (not in public docs) |
Revision as of 22:32, 9 February 2011
RelEng App Store
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
source for buildbot is at http://hg.mozilla.org/build/buildbot/
clobberer
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
- if python, what python modules - can they be run in a virtualenv
- if perl, what cpan modules are needed
- if php, what php version and what php.ini entries are needed
- what is the command line parameters to start the web service
- does it have any special configuration or init files
- does it require root or sudo
- does it require a special directory layout
- will it generate/use temp files or non-database assets?
- what version of mysql and what database config, where is the sql to init the tables
- 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
- cronjobs that need to be run
- 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)