Build

Version 1 by Robin Shen
on Dec 24, 2009 08:09.

 
compared with
Version 2 by Robin Shen
on Jun 10, 2010 03:30.

Changes from 2 to 3 >>
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

 Build is generated by running a configuration. When a particular configuration is triggered (either by user or by the scheduling system), the _build condition_ of the configuration is evaluated. If the result of the evaluation is _true_, the configuration will be run to generate a new build.
   
 {anchor:build version}
 Build version can be used to identify a build inside a configuration, for example: _1.0.0_. Some special version can be used to identify latest build of different status:
 ||Version||Explanation||
 |latest|represents latest build of a configuration|
 |latest_finished|represents latest finished build of a configuration|
 |latest_successful|represents latest successful build of a configuration|
 |latest_recommended|represents latest recommended build of a configuration|
 |latest_failed|represents latest failed build of a configuration|
 |latest_cancelled|represents latest cancelled build of a configuration|
 |latest_running|represents latest running build of a configuration|
  
 {anchor:build name}
 Build name can be used to uniquely identify a build inside the system. It is in the format of _<configuration id>:<build version>_, where _<configuration id>_ represents id of a configuration, and _<build version>_ represents version of a build (including special version as introduced above). Some examples:
 ||Name||Explanation||
 |1:1.0.0|represents build _1.0.0_ in configuration with id _1_|
 |2:latest|represents latest build in configuration with id _2_|
 |2:latest_successful|represents latest successful build in configuration with id _2_|