Use the Gradle bundled plugin to run Gradle builds.
Before you can use the plugin in a chain, you need to install Gradle on an agent and add it as a capability. For details, see Add capabilities to agents.
Configure Gradle plugin
When you add the Gradle plugin to a chain, specify the plugin configuration details.
To configure the Gradle step:
Add the Gradle step to a chain, as described in Create chains.
Enter the plugin configuration details:
Field Description Title Enter a name for the plugin step or accept the default name. Gradle to use Select the Gradle option to use for the build. Execution tasks
(Optional) Specify Gradle task names, separated by spaces. To use the default task, clean build, leave the field empty.
Example: clean build
Working directory (Optional) Enter the build path relative to the stream's root. Use advanced options (optional) Arguments Enter command-line build arguments. Log debug messages Select to log debug messages. This is equivalent to adding the -d Gradle command-line parameter. Print stacktrace Select to print the stacktrace. This is equivalent to adding the -s Gradle command-line parameter. Environment variables
Specify environment variables that override other settings for this chain. Enter each variable on a new line in this format:
Location of Java JDK to use Enter the location of the Java JDK. To use the system JAVA_HOME, leave the field empty. Java options
Enter additional Java options, separated by spaces, for example:
(Optional) Define the control options for the plugin step:
Enable step. By default, the step is enabled to run. Clear this option if you need to deactivate the step.
Disabled steps are skipped when the chain runs.
Ignore unit test counts in reviews, pull requests and changesets. Select this option to exclude the results of post-processing unit tests from the chain run results.
If your chain has several steps of the same type, this option helps prevent the same unit test counts from being reported multiple times.
Fail the step. Specify the conditions for failing the step, such as unit test failures, findings criteria, and/or console log entries.
Mark step as unstable. Specify the conditions for making the step unstable, such as unit test failures, findings criteria, and/or console log entries.
Post processing. Disable all or some post-processing steps that run automatically after the step completes. By default, all post-processing steps are enabled to run.
Output variables (Optional) Specify the output variables to be passed to other steps down the chain. For details, see Publish output variables.