Configuring Rake Builder.

Configuring Rake Builder.
	Chapter 13. Creating the Project Builder(s)

Rake builder a simple Ruby build program with capabilities similar to make.

Name

Provide a name to identify this builder, this name can be changed later.

Command to run Rake

Specify the command to run Rake (normally path to rake.bat). For example: /path/to/rake. String enclosed by ${...} will be interpreted as OGNL expression, and it will be evaluated before execution. Root object used for OGNL expression evaluation here is current Builder object.

	Note
	A single argument that includes spaces should be quoted in order not to be interpreted as multiple arguments.

You can modify the command to add Rake command line options and properties.

Build script path

The path of the Rake build script. If this path is not an absolute path, it is assumed, that it is relative to the project work directory.

Build targets

Specify the target(s) to build. Use space to separate different targets (target name containing spaces should be quoted in order not to be interpreted as multiple targets). If not specified, the default target in the above Rake build file will be build. You can also use OGNL expressions (${...}) to pass variables as the target name. For example you can use ${build.schedule.name} to use different targets for different schedules. Root object used for OGNL expression evaluation here is current Builder object.

Build properties

Define build properties here to pass into the Rake build script. For example:

buildVersion=${build.version}

scheduleName=${build.schedule.name}

You should set one variable per line. OGNL expression can be used to form the value provided it is enclosed by ${...}. Root object used for OGNL expression evaluation here is current Builder object.

Environment variables

Environment variables to set before running this builder. For example:

MYAPP_HOME=${build.schedule.workingDir}

SCHEDULE_NAME=${build.schedule.name}

You should specify one variable per line. OGNL expression can be inserted to form the value, provided they are enclosed by ${...}. Root object used for OGNL expression evaluation here is current Builder object.

Build success condition

The build success condition is an OGNL expression used to determine, if the build of the current project was successful (root object used for OGNL expression evaluation here is current Builder object). If left empty, the result==0 and !builderLogContainsLine("Command failed with status") value is assumed. When this expression evaluates to true, the build is considered successful. Here are some examples to demonstrate format of this OGNL expression:

result==0, here "result" represents return code of Rake execution of the build file.

builderLogContainsLine("^ERROR.*"), the expression will be true if the build's build log contains a line that matches the regular expression pattern "^ERROR.*". Please see http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html for the format of the regular expressions.

The above expressions can be prefixed with a '!' character to inverse the value. For example, !builderLogContainsLine("^ERROR.*") will be true if the build log does not contain a line that matches the specified pattern.

The above expressions can be joined into expression with "and", and "or". For example, the expression result==0 and !builderLogContainsLine("^ERROR.*") will be true if Rake execution of the build returns 0, and the build log does not contain any line starting with "ERROR".


Configuring Maven2 Builder.		Chapter 14. Creating Build Schedule(s) for the Project