View source for ReleaseEngineering/Applications/Clobberer

= 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:

* API
    * http://clobberer.pvt.build.mozilla.org - production API
    * http://clobberer-preproduction.pvt.build.mozilla.org - preproduction API
    * http://clobberer-stage.pvt.build.mozilla.org - staging API

* UI
    * production
        * http://clobberer.pub.build.mozilla.org - http 302
        * https://secure.pub.build.mozilla.org/clobberer - https
    * staging
        * http://clobberer-stage.pub.build.mozilla.org - http 302
        * https://secure.pub.build.mozilla.org/clobberer-stage - https for UI (staging)

= 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 [https://mana.mozilla.org/wiki/display/websites/Releng+web+cluster 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).

= More =
See [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=24805981 the websites page]