ReleaseEngineering/Applications: Difference between revisions

Jump to navigation Jump to search
Line 16: Line 16:
== buildapi ==
== buildapi ==
includes self-serve, wait time reports, pending/running
includes self-serve, wait time reports, pending/running
everything under https://build.mozilla.org/buildapi


source is at http://hg.mozilla.org/build/buildapi
=== Source Code ===
http://hg.mozilla.org/build/buildapi


staging and production instances are running on cruncher, proxied by build.m.o
=== Public Interfaces ===
https://build.mozilla.org/buildapi


uses two mysql slave databases hosted by IT
=== Current Setup ===
production instance is running on cruncher.b.m.o out of
~catlee/buildapi-official. There is a cron job that checks for new changes
every 5 minutes and deploys them. This instance is exposed to the public
behind LDAP auth via the build.m.o url.


uses a memcached daemon running on cruncher
The buildapi instance communicates with a rabbitmq server also running on
cruncher. It also connects to two read-only databases (schedulerdb, statusdb)
on a slave mysql host maintained by IT.


uses a rabbitmq daemon running on cruncher
The self-serve agent, which is responsible for performing many of the job
requests, is running on production-master03 out of ~cltbld/buildapi. It is a
long-running process that waits for messages from the rabbitmq server on
cruncer, and then makes various DB modifications or pokes at masters' web
interfaces. The self-serve agent is started via init, and monitored via
nagios.
 
=== Setup Instructions ===
Described at [[ReleaseEngineering/BuildAPI]]


== slavealloc ==
== slavealloc ==
Confirmed users
2,456

edits

Navigation menu