canmove, Confirmed users
6,439
edits
User:Bhearsum/Balrog/Administration: Difference between revisions
Jump to navigation
Jump to search
User:Bhearsum/Balrog/Administration (view source)
Revision as of 17:29, 5 August 2011
, 5 August 2011no edit summary
No edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
TBD | TBD | ||
== API | = Logging & Rollback = | ||
TBD | |||
= API = | |||
Both the build machine client and the web administration API will make use of the REST interface described below. Status codes of 200 and 500 are implied for success and server error cases. Error responses (4xx and 5xx) will have an 'errmsg' entity in their response. | Both the build machine client and the web administration API will make use of the REST interface described below. Status codes of 200 and 500 are implied for success and server error cases. Error responses (4xx and 5xx) will have an 'errmsg' entity in their response. | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 146: | Line 149: | ||
|} | |} | ||
= Footnotes = | |||
<span id="note1">1. $product-$channel-latest only works in a world where no channel names overlap, which we should be in once 1.9.2 is dead. Doing it this way ensures that we nightly updates work after version bumps happen *and* we don't need to maintain a branch name <-> version mapping a la existing AUS.</span> | <span id="note1">1. $product-$channel-latest only works in a world where no channel names overlap, which we should be in once 1.9.2 is dead. Doing it this way ensures that we nightly updates work after version bumps happen *and* we don't need to maintain a branch name <-> version mapping a la existing AUS.</span> | ||