The Gradle Build Runner runs Gradle projects.
To run builds with Gradle, you need to have Gradle 0.9-rc-1 or higher installed on all the agent machines. |
In this section:
Option | Description |
---|---|
Gradle tasks | Specify Gradle task names separated by spaces. For example: |
Incremental building | 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. |
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. |
Option | Description |
---|---|
Debug | Selecting the Log debug messages check box is equivalent to adding the |
Stacktrace | Selecting the Print stacktrace check box is equivalent to adding the |
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:
task printProperty << { println "${project.ext['teamcity.build.id']}" } |
or if the system property's name is a legal Groovy name identifier (e.g. system.myPropertyName = myPropertyValue
):
task printProperty << { println "$myPropertyName" } |
Code coverage with IDEA code coverage engine and JaCoCo is supported.
See also:
Administrator's Guide: IntelliJ IDEA Code Coverage |