Ant

Path to build.xml file

If you choose the option, you can type the path to an Ant build script file of the project. The path is relative to the project root directory.

tip

Alternatively, click to choose the file using the VCS repository browser (Currently the VCS repository browser is only available for Git, Mercurial, Subversion and Perforce).

Build file content

If you choose this option, click the Type build file content link and type the source code of your custom build file in the text area. Note that the text area is resizeable. Use the Hide link to close the text area.

Working directory

Specify the Build Working Directory if it differs from the checkout directory.

Targets

Use this text field to specify valid Ant targets as a list of space-separated strings. If this field is left empty, the default target specified in the build script file will be run.

Ant home path

Specify the path to the distributive of your custom Ant. You do not need to specify this parameter if you are going to use the Ant distributive bundled with TeamCity (Ant 1.8.2, since TeamCity 8.1, Ant 1.8.4).

note

Please note, that you should use Ant 1.7 if you want to run JUnit4 tests in your builds.

Additional Ant command line parameters

Optionally, specify additional command line parameters as a space-separated list. For example, you can specify the here (see below).

JDK home path

Use this field to specify the path to the JDK which should be used to run the build (launch Ant). If the field is left blank, the value of JAVA_HOME environment variable is used. (The variable can come from the build configuration settings, or agent environment, or properties). If JAVA_HOME is not found, TeamCity uses the Java home of the build agent process itself.

note

Starting with TeamCity 5.1 in many cases agents are able to detect the installed Java automatically. The agent will set appropriate environment variables for each detected Java version: JDK_14, JDK_15, JDK_16 and so on. You can specify the reference to such environment variable in the JDK home path, like: %env.JDK_15%.

References to parameters can generate an Agent Requirements.

JVM command line parameters

You can specify such JVM command line parameters as, for example, maximum heap size or parameters enabling remote debugging. These values are passed by the JVM used to run your build. Example:

-Xmx512m -Xms256m

Reduce test failure feedback time:

Use the following two options to instruct TeamCity to run some tests before others.

Run recently failed tests first

If checked,TeamCity will first run tests failed in the previous finished or running builds as well as tests having a high failure rate (so called blinking tests).

Run new and modified tests first

If checked, before any other test, TeamCity will run the tests added or modified in the change lists included in the running build.