Changes between Version 4 and Version 5 of Master Slave Protocol

Timestamp:

Jun 17, 2005, 1:24:18 AM (19 years ago)

Author:

cmlenz

Comment:

Build requests

Master Slave Protocol

@@ -42 +42 @@
 When the build server detects that builds are necessary for some revision of the project, it queries its database of available slaves and chooses a set of slaves with non-overlapping configurations. For example, if there are 10 clients available that could execute the build of a Java project on Windows 2000 with JDK 1.4, it will only select one of those to actually perform the build.
 
-A build request 
+A build request might look like this (the text is optional and only provided for diagnostic purposes):
 {{{
   MSG 1 1 . 0 78
   Content-Type: application/beep+xml
   
-  <build config="trunk"/>
+  <build>trunk as of revision 492</build>
   END
 }}}
 
-A client can decline a build request (or even abort a build), in which case the build master selects the next available client with the same (or sufficiently similar) configuration.
+A client can decline a build request, in which case the build master selects the next available client with the same (or sufficiently similar) configuration.
 
-If the client accepts a build request, the server will transmit a tarball of the code base that is to be built. The client does not need to know which exact revision (or branch) of the project it is building, nor does it need to perform a checkout itself.
+If the client accepts a build request by sending a positive reply, the server will transmit a tarball of the code base that is to be built. The client does not need to know which exact revision (or branch) of the project it is building, nor does it need to perform a checkout itself.
 
 {{{