Rake

Build runner

Select Rake from the drop-down list.

Path to a Rakefile file

Enter Rakefile path if you don't want to use a default one. Specified path should be relative to the build checkout directory.

Rakefile content

Type in the Rakefile content instead of using existing Rakefile. The new Rakefile will created dynamically from the specified content before running Rake.

Working directory

Optional. Specify if differs from the build checkout directory.

Rake tasks

Enter tasks names separated by space character if you don't want to use 'default' task. For example, 'test:functionals' or 'mytask:test mytask:test2'.

Additional Rake command line parameters

Specified parameters will be added to 'rake' command line. The command line will have the following format:

ruby rake <Additional Rake command line parameters> <TeamCity Rake Runner options, e.g TESTOPTS> <tasks>

Ruby interpreter path

Path to Ruby interpreter (Ruby or JRruby). If not specified the interpreter will be searched in the PATH. In this field you can use values of environment and system variables. For example:

%env.I_AM_DEFINED_IN_BUILDAGENT_CONFIGURATION%

Debug

Check the Track invoke/execute stages option to enable showing Invoke stage data in the build log.

Tests options(TESTOPTS)

Additional options of Test::Unit test runner. If specified, Rake will be invoked with a "TESTOPTS={options}".

RSpec options(SPEC_OPTS)

Additional options of RSpec specs runner. If specified, Rake will be invoked with a "SPEC_OPTS={options}".

Import data from

Select report format from a drop-down list. The following report formats are supported: PMD, Surefire, Ant JUnit, NUnit, and FindBugs.