Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
 |
You are viewing documentation of TeamCity 6.5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
|
|
Search
Table of Contents
|
In order to run builds with Gradle, you need to have Gradle 0.9-rc-1 or higher installed on at least one build agent. Alternatively, if you use Gradle wrapper, you should have properly configured Gradle Wrapper scripts checked in to your Version Control.
In this section:
Gradle Parameters
Option |
Description |
Gradle tasks |
Specify Gradle task names separated by space. For example: :myproject:clean :myproject:build or clean build. If this field is left blank, the 'default' is used. Note, that TeamCity currently supports building Java projects with Gradle. Groovy/Scala/etc. projects building is not tested. |
Gradle home path |
Specify here the path to the Gradle home directory (parent of bin directory). If not specified TeamCity will use 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 above fields. In this case, Gradle specified in Gradle home path and the one installed on agent, are ignored. |
Launching Parameters
Option |
Description |
Debug |
Selecting the Log debug messages check box is equal to adding -d as Gradle command line parameter. |
Stacktrace |
Selecting the Print stacktrace check bos equals to adding -s as Gradle command line parameter. |
Java Parameters
Option |
Description
|
JDK home path |
Use this field to specify the path to your custom JDK which should be 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 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, for example, maximum heap size or parameters enabling remote debugging. These values are passed by the JVM used to run your build.
Example:
|
Code Coverage
To learn about configuring code coverage options with IDEA code coverage engine, please refer to the corresponding page.
See also:
|