The command-line interface is one of the primary methods of interacting with Gradle. The following serves as a reference of executing and customizing Gradle use of a command-line or when writing scripts or configuring continuous integration.
Use of the Gradle Wrapper is highly encouraged. You should substitute
gradle in all following examples when using the Wrapper.
Executing Gradle on the command-line conforms to the following structure. Options are allowed before and after task names.
gradle [taskName...] [--option-name...]
If multiple tasks are specified, they should be separated with a space.
Options that accept values can be specified with or without
= between the option and argument; however, use of
= is recommended.
Options that enable behavior have long-form options with inverses specified with
--no-. The following are opposites.
Many long-form options, have short option equivalents. The following are equivalent:
Many command-line flags can be specified in
The following sections describe use of the Gradle command-line interface, grouped roughly by user goal. Some plugins also add their own command line options, for example
--tests for Java test filtering. For more information on exposing command line options for your own tasks, see Declaring and using command-line options.
You can run a task and all of its dependencies.
$ gradle myTask
You can learn about what projects and tasks are available in the project reporting section.
Most builds support a common set of tasks known as lifecycle tasks. These include the
In a multi-project build, subproject tasks can be executed with ":" separating subproject name and task name. The following are equivalent when run from the root project.
$ gradle :mySubproject:taskName $ gradle mySubproject:taskName
You can also run a task for all subprojects using the task name only. For example, this will run the "test" task for all subprojects when invoked from the root project directory.
$ gradle test
When invoking Gradle from within a subproject, the project name should be omitted:
$ cd mySubproject $ gradle taskName
When executing the Gradle Wrapper from subprojects, one must reference
You can also specify multiple tasks. For example, the following will execute the
deploy tasks in the order that they are listed on the command-line and will also execute the dependencies for each task.
$ gradle test deploy
You can exclude a task from being executed using the
--exclude-task command-line option and providing the name of the task to exclude.
$ gradle dist --exclude-task test > Task :compile compiling source > Task :dist building the distribution BUILD SUCCESSFUL in 0s 2 actionable tasks: 2 executed
You can see that the
test task is not executed, even though it is a dependency of the
dist task. The
test task’s dependencies such as
compileTest are not executed either. Those dependencies of
test that are required by another task, such as
compile, are still executed.
You can force Gradle to execute all tasks ignoring up-to-date checks using the
$ gradle test --rerun-tasks
This will force
test and all task dependencies of
test to execute. It’s a little like running
gradle clean test, but without the build’s generated output being deleted.
By default, Gradle will abort execution and fail the build as soon as any task fails. This allows the build to complete sooner, but hides other failures that would have occurred. In order to discover as many failures as possible in a single build execution, you can use the
$ gradle test --continue
When executed with
--continue, Gradle will execute every task to be executed where all of the dependencies for that task completed without failure, instead of stopping as soon as the first failure is encountered. Each of the encountered failures will be reported at the end of the build.
If a task fails, any subsequent tasks that were depending on it will not be executed. For example, tests will not run if there is a compilation failure in the code under test; because the test task will depend on the compilation task (either directly or indirectly).
When you specify tasks on the command-line, you don’t have to provide the full name of the task. You only need to provide enough of the task name to uniquely identify the task. For example, it’s likely
gradle che is enough for Gradle to identify the
You can also abbreviate each word in a camel case task name. For example, you can execute task
compileTest by running
gradle compTest or even
$ gradle cT > Task :compile compiling source > Task :compileTest compiling unit tests BUILD SUCCESSFUL in 0s 2 actionable tasks: 2 executed
You can also use these abbreviations with the -x command-line option.
The following are task conventions applied by built-in and most major Gradle plugins.
It is common in Gradle builds for the
build task to designate assembling all outputs and running all checks.
$ gradle build
It is common for applications to be run with the
run task, which assembles the application and executes some script or binary.
$ gradle run
It is common for all verification tasks, including tests and linting, to be executed using the
$ gradle check
You can delete the contents of the build directory using the
clean task, though doing so will cause pre-computed outputs to be lost, causing significant additional build time for the subsequent task execution.
$ gradle clean
Gradle provides several built-in tasks which show particular details of your build. This can be useful for understanding the structure and dependencies of your build, and for debugging problems.
You can get basic help about available reporting options using
gradle projects gives you a list of the sub-projects of the selected project, displayed in a hierarchy.
$ gradle projects
You also get a project report within build scans. Learn more about creating build scans.
gradle tasks gives you a list of the main tasks of the selected project. This report shows the default tasks for the project, if any, and a description for each task.
$ gradle tasks
By default, this report shows only those tasks which have been assigned to a task group. You can obtain more information in the task listing using the
$ gradle tasks --all
If you need to be more precise, you can display only the tasks from a specific group using the
$ gradle tasks --group="build setup"
gradle help --task someTask gives you detailed information about a specific task.
$ gradle -q help --task libs Detailed task information for libs Paths :api:libs :webapp:libs Type Task (org.gradle.api.Task) Description Builds the JAR Group build
This information includes the full task path, the task type, possible command line options and the description of the given task.
Build scans give a full, visual report of what dependencies exist on which configurations, transitive dependencies, and dependency version selection.
$ gradle myTask --scan
This will give you a link to a web-based report, where you can find dependency information like this.
Learn more in Inspecting Dependencies.
gradle dependencies gives you a list of the dependencies of the selected project, broken down by configuration. For each configuration, the direct and transitive dependencies of that configuration are shown in a tree. Below is an example of this report:
$ gradle dependencies
Concrete examples of build scripts and output available in the Inspecting Dependencies.
gradle buildEnvironment visualises the buildscript dependencies of the selected project, similarly to how
gradle dependencies visualizes the dependencies of the software being built.
$ gradle buildEnvironment
gradle dependencyInsight gives you an insight into a particular dependency (or dependencies) that match specified input.
$ gradle dependencyInsight
Since a dependency report can get large, it can be useful to restrict the report to a particular configuration. This is achieved with the optional
gradle properties gives you a list of the properties of the selected project.
$ gradle -q api:properties ------------------------------------------------------------ Project :api - The shared API for the application ------------------------------------------------------------ allprojects: [project ':api'] ant: org.gradle.api.internal.project.DefaultAntBuilder@12345 antBuilderFactory: org.gradle.api.internal.project.DefaultAntBuilderFactory@12345 artifacts: org.gradle.api.internal.artifacts.dsl.DefaultArtifactHandler_Decorated@12345 asDynamicObject: DynamicObject for project ':api' baseClassLoaderScope: org.gradle.api.internal.initialization.DefaultClassLoaderScope@12345
Gradle provides bash and zsh tab completion support for tasks, options, and Gradle properties through gradle-completion, installed separately.
Shows a help message with all available CLI options.
Prints Gradle, Groovy, Ant, JVM, and operating system version information.
Print out the full (very verbose) stacktrace for any exceptions. See also logging options.
Print out the stacktrace also for user exceptions (e.g. compile error). See also logging options.
Create a build scan with fine-grained information about all aspects of your Gradle build.
Debug Gradle client (non-Daemon) process. Gradle will wait for you to attach a debugger at
Debug Gradle Daemon process.
Try these options when optimizing build performance. Learn more about improving performance of Gradle builds here.
Many of these options can be specified in
gradle.properties so command-line flags are not necessary. See the configuring build environment guide.
Toggles the Gradle build cache. Gradle will try to reuse outputs from previous builds. Default is off.
Toggles Configure-on-demand. Only relevant projects are configured in this build run. Default is off.
Sets maximum number of workers that Gradle may use. Default is number of processors.
Build projects in parallel. For limitations of this option, see Parallel Project Execution. Default is off.
Specifies the scheduling priority for the Gradle daemon and all processes launched by it. Values are
low. Default is normal.
Generates a high-level performance report in the
Generate a build scan with detailed performance diagnostics.
You can manage the Gradle Daemon through the following command line options.
Use the Gradle Daemon to run the build. Starts the daemon if not running or existing daemon busy. Default is on.
Starts the Gradle Daemon in a foreground process.
gradle --statusto list running and recently stopped Gradle daemons. Only displays daemons of the same Gradle version.
gradle --stopto stop all Gradle Daemons of the same version.
-Dorg.gradle.daemon.idletimeout=(number of milliseconds)
Gradle Daemon will stop itself after this number of milliseconds of idle time. Default is 10800000 (3 hours).
You can customize the verbosity of Gradle logging with the following options, ordered from least verbose to most verbose. Learn more in the logging documentation.
Set logging level via Gradle properties.
Log errors only.
Set log level to warn.
Set log level to info.
Log in debug mode (includes normal stacktrace).
Lifecycle is the default log level.
You can control the use of rich output (colors and font variants) by specifying the "console" mode in the following ways:
Specify console mode via Gradle properties. Different modes described immediately below.
Specifies which type of console output to generate.
plainto generate plain text only. This option disables all color and other rich output in the console output. This is the default when Gradle is not attached to a terminal.
auto(the default) to enable color and other rich output in the console output when the build process is attached to a console, or to generate plain text only when not attached to a console. This is the default when Gradle is attached to a terminal.
richto enable color and other rich output in the console output, regardless of whether the build process is not attached to a console. When not attached to a console, the build output will use ANSI control characters to generate the rich output.
verboseto enable color and other rich output like the
rich, but output task names and outcomes at the lifecycle log level, as is done by default in Gradle 3.5 and earlier.
By default, Gradle won’t display all warnings (e.g. deprecation warnings). Instead, Gradle will collect them and render a summary at the end of the build like:
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
You can control the verbosity of warnings on the console with the following options:
Specify warning mode via Gradle properties. Different modes described immediately below.
Specifies how to log warnings. Default is
allto log all warnings.
summaryto suppress all warnings and log a summary at the end of the build.
noneto suppress all warnings, including the summary at the end of the build.
Gradle’s rich console displays extra information while builds are running.
Progress bar and timer visually describe overall status
Parallel work-in-progress lines below describe what is happening now
Colors and fonts are used to highlight important output and errors
The following options affect how builds are executed, by changing what is built or how dependencies are resolved.
Run the build as a composite, including the specified build. See Composite Builds.
Specifies that the build should operate without accessing network resources. Learn more about options to override dependency caching.
Refresh the state of dependencies. Learn more about how to use this in the dependency management docs.
Run Gradle with all task actions disabled. Use this to show which task would have executed.
Indicates that all resolved configurations that are lockable should have their lock state persisted. Learn more about this in dependency locking.
Indicates that versions for the specified modules have to be updated in the lock file. This flag also implies
--write-locks. Learn more about this in dependency locking.
Do not rebuild project dependencies. Useful for debugging and fine-tuning
buildSrc, but can lead to wrong results. Use with caution!
You can customize many aspects about where build scripts, settings, caches, and so on through the options below. Learn more about customizing your build environment.
Specifies the build file. For example:
gradle --build-file=foo.gradle. The default is
Specifies the settings file. For example:
Specifies the Gradle user home directory. The default is the
.gradledirectory in the user’s home directory.
Specifies the start directory for Gradle. Defaults to current directory.
Specifies the project-specific cache directory. Default value is
.gradlein the root project directory.
Sets a system property of the JVM, for example
-Dmyprop=myvalue. See System Properties.
Specifies an initialization script. See Init Scripts.
Sets a project property of the root project, for example
-Pmyprop=myvalue. See System Properties.
Set JVM arguments.
Set JDK home dir.
Use the built-in
gradle init task to create a new Gradle builds, with new or existing projects.
$ gradle init
Most of the time you’ll want to specify a project type. Available types include
java-application, and more. See init plugin documentation for details.
$ gradle init --type java-library
gradle wrapper task generates a script,
gradlew, that invokes a declared version of Gradle, downloading it beforehand if necessary.
$ gradle wrapper --gradle-version=4.4
You can also specify
--gradle-distribution-sha256-sum in addition to
--gradle-version. Full details on how to use these options are documented in the Gradle wrapper section.
Continuous Build allows you to automatically re-execute the requested tasks when task inputs change.
For example, you can continuously run the
test task and all dependent tasks by running:
$ gradle test --continuous
Gradle will behave as if you ran
gradle test after a change to sources or tests that contribute to the requested tasks. This means that unrelated changes (such as changes to build scripts) will not trigger a rebuild. In order to incorporate build logic changes, the continuous build must be restarted manually.
If Gradle is attached to an interactive input source, such as a terminal, the continuous build can be exited by pressing
CTRL-D (On Microsoft Windows, it is required to also press
CTRL-D). If Gradle is not attached to an interactive input source (e.g. is running as part of a script), the build process must be terminated (e.g. using the
kill command or similar). If the build is being executed via the Tooling API, the build can be cancelled using the Tooling API’s cancellation mechanism.
There are several issues to be aware with the current implementation of continuous build. These are likely to be addressed in future Gradle releases.
Gradle starts watching for changes just before a task executes. If a task modifies its own inputs while executing, Gradle will detect the change and trigger a new build. If every time the task executes, the inputs are modified again, the build will be triggered again. This isn’t unique to continuous build. A task that modifies its own inputs will never be considered up-to-date when run "normally" without continuous build.
If your build enters a build cycle like this, you can track down the task by looking at the list of files reported changed by Gradle. After identifying the file(s) that are changed during each build, you should look for a task that has that file as an input. In some cases, it may be obvious (e.g., a Java file is compiled with
compileJava). In other cases, you can use
--info logging to find the task that is out-of-date due to the identified files.
Due to class access restrictions related to Java 9, Gradle cannot set some operating system specific options, which means that:
On macOS, Gradle will poll for file changes every 10 seconds instead of every 2 seconds.
On Windows, Gradle must use individual file watches (like on Linux/Mac OS), which may cause continuous build to no longer work on very large projects.
The JDK file watching facility relies on inefficient file system polling on macOS (see: JDK-7133447). This can significantly delay notification of changes on large projects with many source files.
Additionally, the watching mechanism may deadlock under heavy load on macOS (see: JDK-8079620). This will manifest as Gradle appearing not to notice file changes. If you suspect this is occurring, exit continuous build and start again.
On Linux, OpenJDK’s implementation of the file watch service can sometimes miss file system events (see: JDK-8145981).
Creating or removing symbolic link to files will initiate a build.
Modifying the target of a symbolic link will not cause a rebuild.
Creating or removing symbolic links to directories will not cause rebuilds.
Creating new files in the target directory of a symbolic link will not cause a rebuild.
Deleting the target directory will not cause a rebuild.
The current implementation does not recalculate the build model on subsequent builds. This means that changes to task configuration, or any other change to the build model, are effectively ignored.