Changes between Version 6 and Version 7 of Master Slave Protocol Http

Timestamp:

Jul 24, 2007, 3:56:30 PM (17 years ago)

Author:

cmlenz

Comment:

--

Master Slave Protocol Http

@@ -145 +145 @@
 
 The server responds with a `201 Created` response.
+
+== Cancelling Builds ==
+
+Using the BEEP protocol, the build master would mark builds as aborted if the connection to the slave was closed unexpectedly. This is no longer possible when using HTTP.
+
+To handle the case of build slaves going away at some point between having created a build and completing the build, the build master should have a configurable timeout. All in-progress builds would be checked against this timeout; if there has been no activity on the build for an amount of time exceeding the timeout, the master should cancel the build, resetting it the `PENDING` state. If a slave later '''does''' decide to come back to life and post results, it would get 404 (Not Found) or 409 (Conflict) errors, and should cancel the build on its side, too.
+
+There should probably be a background thread posting heartbeat requests to the master while lengthy build steps are executed.