Changes between Version 4 and Version 5 of Build Configurations

Timestamp:

Sep 12, 2005, 3:28:58 PM (19 years ago)

Author:

cmlenz

Comment:

Added headings for more structure

Build Configurations

@@ -16 +16 @@
 Technically, a target platform is a named set of rules against which the properties of build slaves are matched. Each rule is a regular expression matching a particular slave property, such as the operating system or the processor. When a slave connects to the build master, it sends a registration message that includes information about the slave.
 
+=== Slave Properties ===
+
 By default, the following properties are included:
 
@@ -25 +27 @@
 
 Note that not all of these properties may be available for all platforms. For example, the `machine` and `processor` properties are currently empty for build slaves running on Windows. Additional properties can be set up on the slave side using a [wiki:SlaveConfiguration configuration file].
+
+=== Examples ===
 
 So to set up a target platform, you create rules that are checked against the properties of the slave. For example, a target platform that matches slave running Linux on x86 would look like this:
@@ -37 +41 @@
 || `family` || `^nt$` ||
 
+
 The build master will request a build from at most one slave for every target platform. So, for example, if there are three slaves connected that are running NetBSD on x86, only one of them will perform the build of a specific revision. Slaves that match a particular target platform are treated as if they were completely interchangable.