Ant

This is a runner for Ant build.xml files. TeamCity comes bundled with Ant 1.8.4., since TeamCity 9.1 - with Ant 1.9.6.

Testing Frameworks Support

The TeamCity Ant runner supports the JUnit and TestNG frameworks. When tests are run by the junit and testng tasks directly within the script, TeamCity reports tests on the fly.

By using the <parallel> tag in your Ant script, it is possible to have the JUnit and TestNG tasks run in parallel. TeamCity supports this and should concurrently log the parallel processes correctly.

Reporting and Logging

TeamCity collects detailed data from Ant as to the performed activities, provides structured error reporting, and reports tests. However, you can start a build with no specific reporting or to turn off TeamCity-specific logging:

To disable TeamCity-specific reporting in Ant, use teamcity.ant.listener.enabled=false build configuration parameter
To disable JUnit reporting, use teamcity.ant.junit-support.enabled=false system property
To disable TestNG reporting, use teamcity.ant.testng-support.enabled=false system property

Ant Runner Settings

Ant Parameters

Option	Description
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. Alternatively, click to choose the file using the VCS repository browser.
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. 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. 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.4; since TeamCity 9.1- Ant 1.9.6. 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).

ant-net-tasks Tool

The Ant build runner comes with a bundled tool, ant-net-tasks, which includes the jar files required for network tasks, such as FTP, sshexec, scp and mail. It also contains missing link Ant task which can be used for REST requests.

To use the tool, specify -lib "%\teamcity.tool.ant-net-tasks%" in Additional Ant command line parameters of the runner settings.

Java Parameters

Option	Description
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. 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 implicit requirement.
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

Option

Description

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.

References to parameters can generate an implicit requirement.

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

antTestParametersTest parameters

Tests reordering works the following way: TeamCity provides tests that should be run first (test classes), after that, when a JUnit task starts, it checks whether it includes these tests. If at least one test is included, TeamCity generates a new fileset containing included tests only and processes it before all other filesets. It also patches other filesets to exclude tests added to the automatically generated fileset. After that JUnit starts and runs as usual.

Option	Description
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, TeamCity will first run the tests added or modified in the change lists included in the running build.

Option

Description

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, TeamCity will first run the tests added or modified in the change lists included in the running build.

Code Coverage

To learn about configuring code coverage options, refer to the Configuring Java Code Coverage page.

Last modified: 20 April 2023