Edgewall Software

Changes between Version 2 and Version 3 of Build Configurations


Ignore:
Timestamp:
Jul 1, 2005, 5:44:12 PM (19 years ago)
Author:
cmlenz
Comment:

Replace "tree" with "path"

Legend:

Unmodified
Added
Removed
Modified
  • Build Configurations

    v2 v3  
    44
    55A build configuration is composed of:
    6  * the ''tree'' (aka branch) of the repository that should be built,
     6 * a path (or branch name) that identifies the subset of the repository that should be built,
    77 * a flag to temporarily or permanently deactivate builds of that tree,
    88 * a “pretty” name for display, as well as a description that may contain [wiki:WikiFormatting wiki formatting], and
     
    1111== Target platforms ==
    1212
    13 A target platform is something like ''“NetBSD on x86”'' or ''“Win32 with Java 1.4”''. Technically, a target platform is a named set of rules against which build slaves are matched. Each rule is a regular expression matching a particular slave property, such as the operating system or the processor.
     13A target platform is something like ''“NetBSD on x86”'' or ''“Win32 with Java 1.4”''. 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.
    1414
    15 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.
     15The 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.
    1616
    1717If a slave connects that doesn't match any of the configured target platforms, the build master will reject its registration.
    18 
    19  '''TODO''': ''What about overlapping rules?''