ReleaseEngineering/How To/Manage Buildbot with Fabric: Difference between revisions

ReleaseEngineering/How To/Manage Buildbot with Fabric (view source)

85 bytes added , 21 December 2012

added graceful_restart option

Confirmed users

1,364

edits

@@ Line 179: / Line 179: @@
 If the reconfig gets stuck, see [https://wiki.mozilla.org/ReleaseEngineering/How_To/Unstick_a_Stuck_Slave_From_A_Master How To/Unstick a Stuck Slave From A Master].
-As a special case for test masters, you can trigger a "Clean Shutdown" from the web UI for that master. After jobs complete, the master will shut down (web page will not be served). Fabric should notice and unstick itself at that point. If fabric doesn't notice, in a separate window, individually do the update and start steps. If fabric still doesn't notice, good luck and document what works.
+As a special case for test masters, you can unstick things by either:
+* triggering a "Clean Shutdown" from the web UI for that master, or
+* using manage_masters.py graceful_restart command
+After jobs complete, the master will shut down (web page will not be served). Fabric should notice and unstick itself at that point. If fabric doesn't notice, in a separate window, individually do the update and start steps. If fabric still doesn't notice, good luck and document what works.