ReleaseEngineering/Applications/Clobberer

From MozillaWiki
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:

  • API
   * http://clobberer.pvt.build.mozilla.org - production API
   * http://clobberer-preproduction.pvt.build.mozilla.org - preproduction API
   * https://api-pub-build.allizom.org/clobberer/lastclobber - staging API
  • UI
   * production
       * http://clobberer.pub.build.mozilla.org - http 302
       * https://secure.pub.build.mozilla.org/clobberer - https
   * staging
       * https://api-pub-build.allizom.org/clobberer

Requirements

Python

MySQL-python

Resources

Security

Clobberer uses the LDAP username verified and supplied by Apache, with some users having slightly elevated priviledges (the ability to clobber release jobs).

Testing/Updating

Clobberer is a Flask blueprint, and part of the RelengAPI project. For information about Testing/Updating see the project readme: https://github.com/mozilla/build-relengapi-clobberer

More

See the websites page