Gradle tasks | Specify Gradle task names separated by spaces. For example: :myproject:clean :myproject:build or clean build . If this field is left blank, the 'default' task is used. Note that TeamCity currently supports building Java projects with Gradle. B uilding Groovy/Scala/etc. projects has not been tested. |
Incremental building | TeamCity can make use of the Gradle :buildDependents feature. If the Incremental building checkbox is enabled, TeamCity will detect Gradle modules affected by changes in the build, and start the :buildDependents command for them only. This will cause Gradle to fully build and test only the modules affected by changes. |
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 GRADLE_HOME environment variable. If you don't have Gradle installed on agents, you can use Gradle wrapper instead. |
Additional Gradle command line parameters | Optionally, specify the space-separated list of command line parameters to be passed to Gradle. |
Gradle Wrapper | 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. |