ReleaseEngineering/Applications/Clobberer
Jump to navigation
Jump to search
Application Description
The clobberer allows developers to "clobber" particular build directories (objdirs) on particular slaves. This is sometimes necessary if a change is committed that is not compatible with previous objdirs, or occasionally when a compile failure results in a bogus objdir.
The application has an outward-facing web interface for developers, and also provides an internal web service which buildslaves contact to determine what build directories they should clobber.
There are several vhosts involved here:
clobberer.pvt.build.mozilla.org - production API clobberer-preproduction.pvt.build.mozilla.org - preproduction API clobberer-stage.pvt.build.mozilla.org - staging API clobberer.pub.build.mozilla.org - http entry point for UI (production) clobberer-staging.pub.build.mozilla.org - http entry point for UI (staging) secure.pub.build.mozilla.org - https for UI (staging and production)
Requirements
- MySQL server (SQLite is also possible, but we are using MySQL in production and staging)
- PHP and Apache
Resources
- two MySQL databases (production and staging)
- runs on the releng web cluster
Security
Clobberer uses the LDAP username verified and supplied by Apache, with some users having slightly elevated priviledges (the ability to clobber release jobs).