ReleaseEngineering/Applications/Clobberer: Difference between revisions

ReleaseEngineering/Applications/Clobberer (view source)

273 bytes removed , 14 November 2014

no edit summary

78

edits

@@ 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.
-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
      * 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
          * https://api-pub-build.allizom.org/clobberer
@@ Line 20: / Line 16: @@
 = Requirements =
 Python
-MySQL-python (if using a MySQL backend)
 = Resources =
@@ Line 28: / Line 22: @@
 = 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 =