The NAnt build runner allows using NAnt build files.
TeamCity supports NAnt starting from version 0.85.
MSBuild Task for NAnt
The TeamCity NAnt runner includes a task called
msbuild that allows NAnt to start MSBuild scripts. TeamCity
msbuild task for NAnt has the same set of attributes as the NAntContrib package
msbuild task. The MSBuild build processes started by NAnt will behave exactly as if they were launched by TeamCity MSBuild/SLN2005 build runner (that is
NUnitTeamCity MSBuild tasks will be added to build scripts and logs and error reports will be sent directly to the build server).
By default, NAnt
msbuild task checks for current value of NAnt target-framework property to select MSBuild runtime version.
This parameter could be overriden by setting
teamcity_dotnet_tools_version project property with required .NET Framework version, i.e. "4.0".
<nunit2> Task for NAnt
To test all the assemblies without halting on first failed test use:
Below you can find reference information about NAnt Build Runner fields.
Path to a build file
Specify path relative to the Build Checkout Directory.
Build file content
Select the option, if you want to use a different build script than the one listed in the settings of the build file. When the option is enabled, you have to type the build script in the text area.
Specify the names of build targets defined by the build script, separated by spaces. The available targets can be viewed in the Web UI by clicking the icon next to the field and added by checking the appropriate boxes.
Specify the path to the Build Working Directory. By default, the build working directory is set to the same path as the build checkout directory.
Enter a path to the
Command line parameters
Specify any additional parameters for
Reduce test failure feedback time
Use following option to instruct TeamCity to run some tests before others.
Run recently failed tests first
If checked, in the first place TeamCity will run tests failed in previous finished or running builds as well as tests having high failure rate (a so called blinking tests).
To learn about configuring code coverage options, refer to the Configuring .NET Code Coverage page.