IntelliJ IDEA Project

Java

Runner is able to compile Java projects

JUnit 3.x/4.x

, with limitations

• Test runner parameters are not supported

• running Maven before tests start is not supported

• alternative JRE is not supported

TestNG

, with limitations

• Test runner parameters are not supported

• running Maven before tests start is not supported

• running of the tests from group is not supported

• alternative JRE is not supported

Application run configuration

, with limitations

• running Maven before tests start is not supported

• alternative JRE is not supported

J2EE integration

Runner is able to produce WAR and EAR archives with necessary descriptors

JPA

Runner adds necessary descriptors in produced artifacts

GWT

Runner can invoke GWT compiler and add compiler result to artifacts

Groovy

, with limitations

Runner is able to compile projects with Groovy code and run tests written in Groovy, Groovy script run configurations are not supported

Android

Flex

Coverage

, if specified in run configurations

IntelliJ IDEA based coverage can be configured separately on the runner settings page

Profiling plugins

<path_variable_name>

This field appears, if the project file contains path macros, defined in the Path Variables dialog of IntelliJ IDEA's Settings dialog. In the Set value to field, specify a path to project resources, to be used on different build agents.

JDK Home

Use this field to specify JDK home for the project.

JDK Jar File Patterns

Click this link to open a text area, where you can define templates for the .jar files of the project JDK. Use Ant rules to define the .jar file patterns.
The default value is used for Linux and Windows operating systems:

For macOS, use the following lines:

IDEA Home

If your project uses the IDEA JDK, specify the location of IDEA home directory

IDEA Jar Files Patterns

Click this link to open a text area, where you can define templates for the .jar files of the IDEA JDK.

JDK

Select a JDK. This section details the available options. The default is JAVA_HOME environment variable or the agent's own Java.

JDK home path

The option is available when <Custom> is selected above. Use this field to specify the path to your custom JDK used to run the build. If the field is left blank, the path to JDK Home is read either from the JAVA_HOME environment variable on the agent machine, or from the env.JAVA_HOME property specified in the build agent configuration file (buildAgent.properties). If these values are not specified, TeamCity uses the Java home of the build agent process itself.

JVM command line parameters

Additional JVM command line parameters allow you to set initial and maximum heap sizes, enable additional logging, select the required bytecode verifier mode, and more.

You can specify both standard (begin with -, for instance -verbose:[class|module|gc|jni] or --dry-run) and non-standard (begin with -X, for instance -Xmx<size> or -XstartOnFirstThread) JVM options.

To specify multiple command line parameters, use space as a separator. For example:

Only compile classes required to build artifacts and execute run configurations

Select whether to compile all classes in the project or only those classes which are required by run configurations or for building artifacts.

Artifacts to Build

Specify here names of the artifacts to be built that are configured in the IntelliJ IDEA project.

Run configurations to execute

Specify here names of IntelliJ IDEA run configurations configured in the project to execute inside TeamCity build. Supported configuration types are: JUnit, TestNG, and Application. Note that run configurations specified here should be shared (via "Share" checkbox in IntelliJ IDEA Run/Debug Configurations dialog) and checked in to the version control.

Ant and Build Artifacts tasks specified in the Before launch list of IDEA run configurations are supported.