Force Gradle to Run Test Again

Y'all can learn about what projects and tasks are available in the project reporting section. Most builds support a common set of tasks known equally lifecycle tasks. These include the build, get together, and cheque tasks.

In order to execute a task called "myTask" on the root projection, type:

This volition run the unmarried "myTask" and as well all of its job dependencies.

Executing tasks in multi-project builds

In a multi-project build, subproject tasks tin be executed with ":" separating subproject name and task name. The following are equivalent when run from the root projection:

$ gradle :my-subproject:taskName $ gradle my-subproject:taskName

You lot can as well run a task for all subprojects past using a chore selector that consists of the task name only. For case, this will run the "examination" task for all subprojects when invoked from the root project directory:

Some tasks selectors, like help or dependencies, will only run the task on the project they are invoked on and non on all the subprojects. The chief motivation for this is that these tasks print out information that would be hard to process if it combined the data from all projects.

When invoking Gradle from within a subproject, the project name should be omitted:

$ cd my-subproject $ gradle taskName

When executing the Gradle Wrapper from subprojects, i must reference gradlew relatively. For example: ../gradlew taskName. The community gdub projection aims to make this more than convenient.

Executing multiple tasks

You can also specify multiple tasks. For example, the following will execute the test and deploy tasks in the club that they are listed on the command-line and will besides execute the dependencies for each task.

Excluding tasks from execution

You can exclude a chore from being executed using the -10 or --exclude-chore control-line option and providing the name of the chore to exclude.

Effigy one. Simple Job Graph

Excluding tasks

$ gradle dist --exclude-task test  > Task :compile compiling source  > Task :dist building the distribution  BUILD SUCCESSFUL in 0s 2 actionable tasks: two executed

You lot can see that the test chore is non executed, fifty-fifty though it is a dependency of the dist task. The examination task'due south dependencies such as compileTest are not executed either. Those dependencies of test that are required past another task, such every bit compile, are still executed.

Forcing tasks to execute

You tin can strength Gradle to execute all tasks ignoring up-to-date checks using the --rerun-tasks option:

$ gradle test --rerun-tasks

This will forcefulness examination and all job dependencies of test to execute. It's a piddling like running gradle make clean exam, but without the build'southward generated output being deleted.

Continuing the build when a failure occurs

Past default, Gradle will abort execution and fail the build every bit soon as whatsoever task fails. This allows the build to consummate sooner, but hides other failures that would have occurred. In club to detect as many failures as possible in a single build execution, y'all tin use the --go along option.

When executed with --continue, Gradle volition execute every task to be executed where all of the dependencies for that task completed without failure, instead of stopping equally shortly as the first failure is encountered. Each of the encountered failures will exist reported at the end of the build.

If a job fails, any subsequent tasks that were depending on it will not be executed. For case, tests will not run if at that place is a compilation failure in the code nether test; because the examination task will depend on the compilation chore (either directly or indirectly).

Name abbreviation

When you lot specify tasks on the command-line, y'all don't have to provide the total name of the chore. You only need to provide enough of the task proper noun to uniquely identify the task. For example, it'south likely gradle che is enough for Gradle to identify the check chore.

The aforementioned applies for project names. You can execute the cheque task in the library subproject with the gradle lib:che command.

Yous can apply camel case patterns for more circuitous abbreviations. These patterns are expanded to match camel case and kebab case names. For example the pattern foBa (or even fB) matches fooBar and foo-bar.

More concretely, you lot tin run the compileTest job in the my-awesome-library subproject with the gradle mAL:cT command.

Abbreviated project and task names

$ gradle  mAL:cT  > Job :my-awesome-library:compileTest compiling unit tests  BUILD SUCCESSFUL in 0s ane actionable task: 1 executed

Y'all can also use these abbreviations with the -x command-line option.

gibsonamis1962.blogspot.com

Source: https://docs.gradle.org/current/userguide/command_line_interface.html

Share this post