Confirmed users
22
edits
ReleaseEngineering/How To/Close or Open the Tree: Difference between revisions
ReleaseEngineering/How To/Close or Open the Tree (view source)
Revision as of 05:32, 19 January 2019
, 19 January 2019Set topic in CI
(Updated the list of repositories to be closed when an infrastructure issue occurs) |
(Set topic in CI) |
||
| Line 5: | Line 5: | ||
** Please use the "Remember previous state" option, so you can easily restore the previous status messages when you are finished (there will be a restore button at the bottom of the page). | ** Please use the "Remember previous state" option, so you can easily restore the previous status messages when you are finished (there will be a restore button at the bottom of the page). | ||
** In order to change tree statuses, your browserID email needs to be added with sheriff permissions (ping edmorley/philor/catlee or ask in #developers). | ** In order to change tree statuses, your browserID email needs to be added with sheriff permissions (ping edmorley/philor/catlee or ask in #developers). | ||
** Set the topic in #ci with the following model: OnDuty: --- ldap --- ALL/ (Name of the trees) CURRENTLY CLOSED --- BUG: bug number --- Unified #releng / #buildduty channels. CI issues? You’ve come to the right place. | This channel is logged at https://mozilla.logbot.info/ci | |||
* Reload TreeStatus to confirm the status has changed. | * Reload TreeStatus to confirm the status has changed. | ||