The Gradle Build Runner runs Gradle projects.
In this section:
Specify Gradle task names separated by space. For example:
TeamCity can make use of Gradle
Gradle home path
Specify here the path to the Gradle home directory (the parent of the bin directory). If not specified, TeamCity will use the Gradle from an agent's
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 check box is equivalent to adding the
Selecting the Print stacktrace check box is equivalent to adding the
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 agent the computer, or from env.JAVA_HOME property specified in the build agent configuration file (buildAgent.properties). If these both values are not specified, TeamCity uses Java home of the build agent process itself.
JVM command line parameters
You can specify such JVM command line parameters as, e.g., 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 (e.g.
system.myPropertyName = myPropertyValue):
An alternative way is using the
teamcity property (deprecated since 9.1.5). The property contains the map with all defined system properties (see Defining and Using Build Parameters for details).
The example below contains a task that will print all available build properties to the build log (it must be executed by the buildserver):