Gradle

Use the Gradle bundled plugin to run Gradle builds.

Prerequisites

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.

Back to top

Configuration

When you add the Gradle plugin step to a chain, specify the following configuration details:

Field Description
Title Enter a name for the plugin step.
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 will override other settings for this chain. Enter each variable on a separate line in this format:

KEY=VALUE

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:

-Xms200m -Xmx700m

Control options

(Optional) Expand Control options and define the following settings:

  • Enable step. Leave this option selected to enable the step to run. Clearing this option deactivates the step.

  • 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 findings criteria and/or log entries.

  • Mark step as unstable. Specify the conditions for making the step unstable, such as findings criteria and/or 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) Enter the variables to be passed to other steps down the chain. For details, see Publish output variables to chain steps.

Back to top

See also: