On this page:
The Gradle Build Runner runs Gradle projects.
Specify Gradle task names separated by spaces. For example:
TeamCity can make use of the Gradle
Gradle home path
Specify here the path to the Gradle home directory (the parent of the
Additional Gradle command line parameters
Optionally, specify the space-separated list of command line parameters to be passed to Gradle.
If this checkbox is selected, TeamCity will look for Gradle Wrapper scripts in the checkout directory, and launch the appropriate script with Gradle tasks and additional command line parameters specified in the fields above. In this case, the Gradle specified in Gradle home path and the one installed on agent, are ignored.
Selecting the Log debug messages checkbox is equivalent to adding the
Selecting the Print stacktrace check box is equivalent to adding the
Select a JDK. This section details the available options. The default is
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
JVM command line parameters
You can specify such JVM command line parameters, for example, maximum heap size or parameters enabling remote debugging. These values are passed by the JVM used to run your build.
The TeamCity system parameters can be accessed in Gradle build scripts in the same way as Gradle properties. The recommended way to reference properties is as follows:
or if the system property's name is a legal Groovy name identifier (for example,
system.myPropertyName = myPropertyValue):
In this section, you can specify a Docker image which will be used to run the build step.
Code coverage with IDEA code coverage engine and JaCoCo is supported.
Administrator's Guide: IntelliJ IDEA Code Coverage