ReleaseEngineering/Applications/Clobberer: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 4: Line 4:
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.
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:
As with all other RelengAPI integrated applications, clobberer is completely API based. For information about its endpoints see:


* API
https://api.pub.build.mozilla.org/clobberer/
    * 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
* UI
     * production
     * production
        * http://clobberer.pub.build.mozilla.org - http 302
         * https://api.pub.build.mozilla.org/clobberer/ - https
         * https://secure.pub.build.mozilla.org/clobberer - https
     * staging
     * staging
         * https://api-pub-build.allizom.org/clobberer
         * https://api-pub-build.allizom.org/clobberer
Line 20: Line 16:
= Requirements =
= Requirements =
Python
Python
MySQL-python (if using a MySQL backend)


= Resources =
= Resources =
Line 28: Line 22:


= Security =
= Security =
Clobberer uses the LDAP username verified and supplied by Apache, with some users having slightly elevated priviledges (the ability to clobber release jobs).
Clobberer uses the LDAP username verified by RelengAPI's permissions system.


= Testing/Updating =
= Testing/Updating =

Revision as of 20:47, 14 November 2014

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.

As with all other RelengAPI integrated applications, clobberer is completely API based. For information about its endpoints see:

https://api.pub.build.mozilla.org/clobberer/

  • UI
   * production
       * https://api.pub.build.mozilla.org/clobberer/ - https
   * staging
       * https://api-pub-build.allizom.org/clobberer

Requirements

Python

Resources

Security

Clobberer uses the LDAP username verified by RelengAPI's permissions system.

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