This page describes how to configure an NAnt builder for a Job. On this page:

Configuring a NAnt Builder for a Job

To configure a NAnt builder for a Job:
If you are creating a new Plan or new Job, start at step 2.

1. Navigate to the Job's configuration pages, as described on Editing a Job.
   
2. In the 'Builder' dropdown, select the NAnt builder that you wish to configure for this plan (e.g. "NAnt"). The builder that you select will become one of the plan's capability requirements. For details please see Configuring a Job's Requirements.
   Tip: If you want to configure a new shared local builder capability in Bamboo, you can do so by clicking the 'Add New Builder' link and entering the builder details in the window that displays. Once you have added the new builder, it will be available for you to select from the 'Builder' dropdown.
3. The screen will refresh to display the builder settings specific to NAnt:
   • 'Build File' — Type the relevant filename (e.g. default.build). You can include variables (see Using Global or Build-specific Variables).
   • 'Target' — Specify the NAnt target that you want Bamboo to execute each time the source code changes. For example: RegexDemo/RegexDemo.sln.  You can also include variables (see Using Global or Build-specific Variables).
   • 'Options' — Specify the NAnt command line options that you want to include (e.g. You can also include variables (see Using Global or Build-specific Variables).
4. If required, update the system environment variables and working directory settings:
5. Update the following build parameters:
   • 'The build will produce XYZ test results' — Select the relevant check boxes (where XYZ is NUnit, MBUnit or MSTest) if you want Bamboo to gather test results data for each build result.
     Bamboo requires test results to be XML files that are compatible with NUnit, MBUnit or MSTest result file formats.
     If one of these check boxes is selected, the following associated field will appear:
     • 'XYZ Test Results File/Directory' (where XYZ is NUnit, MBUnit or MSTest) — Type the name of the test results directory (or multiple directories, separated by commas). You can also use Ant-style patterns such as **/test-reports/*.xml. Please specify file path relative to your Job build's root directory — do not specify an absolute path like /home/bamboouser/bamboo-home/xml-data/build-dir/JOB_KEY/.
6. 
   • 
   • 'NCover output will be produced' — Select this check box if you are running the NCover code coverage tool and want to view its code-coverage data from within Bamboo. The following field will be displayed:
     • 'NCover XML Directory' — Specify the location where Bamboo will look for the XML report output file from NCover. Ensure that you specify file path relative to your Job build's root directory.
       Please do not specify an absolute path like /home/bamboouser/bamboo-home/xml-data/build-dir/JOB_KEY/
   • 'Use Clover to collect Code Coverage for this build' — Do not select this option. Clover now only supports builders of Java-/Groovy-based projects, such as Ant, Maven or Grails.
7. 

Notes

Related Topics

Specifying a Builder
Editing a Job