Gradle Task Dependencies and Ordering: Difference between revisions
Line 35: | Line 35: | ||
If multiple tasks are provides as argument of dependsOn(...), the order in which they are declared does not influence the order in which they are executed. The only thing that is guaranteed is that all will be executed before the task that declares the dependency. | If multiple tasks are provides as argument of dependsOn(...), the order in which they are declared does not influence the order in which they are executed. The only thing that is guaranteed is that all will be executed before the task that declares the dependency. | ||
Other methods that can be used to set explicit dependencies are: | |||
* [https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#setDependsOn-java.lang.Iterable- setDependsOn(Iterable)] | |||
* [https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#mustRunAfter-java.lang.Object...- mustRunAfter(Object...)] | |||
* [https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#setMustRunAfter-java.lang.Iterable- setMustRunAfter(Iterable)] | |||
* [https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#shouldRunAfter-java.lang.Object...- shouldRunAfter(Object ...)] | |||
* [https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#setShouldRunAfter-java.lang.Iterable- setShouldRunAfter(Iterable)] | |||
==Finalizer Tasks== | ==Finalizer Tasks== |
Revision as of 23:07, 8 October 2020
External
- https://docs.gradle.org/current/dsl/org.gradle.api.Task.html#N18D13
- https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#dependencies
Internal
Overview
May times, a task requires another task to run first, especially if the task depends on the produced output of its dependency task. A task may declared its dependencies explicitly. A task may depend on other tasks implicitly, as described in the Implicit Dependencies section.
In Gradle, task execution order is automatically determined taking into account explicit dependencies and implicit dependencies, and a specific execution order of all tasks involved is not guaranteed. The only thing that is guaranteed is that the dependencies will be honored. This architectural decision has several benefits: you don't need to know the whole chain of task dependencies to make a change, and because the tasks don't have to be executed strictly sequentially, they can be parallized.
Explicit Dependencies
The Task API used to declare explicit task dependencies is Task.dependsOn(Object... paths), which surfaces in the DSL as:
task red {
dependsOn 'blue'
...
}
task red(dependsOn: [blue, green] {
...
}
task red {
...
}
red.dependsOn(blue, green)
Note that a task dependency may be another task name, the task instance itself or another objects.
If multiple tasks are provides as argument of dependsOn(...), the order in which they are declared does not influence the order in which they are executed. The only thing that is guaranteed is that all will be executed before the task that declares the dependency.
Other methods that can be used to set explicit dependencies are:
- setDependsOn(Iterable)
- mustRunAfter(Object...)
- setMustRunAfter(Iterable)
- shouldRunAfter(Object ...)
- setShouldRunAfter(Iterable)
Finalizer Tasks
A finalizer task is a task that will be scheduled to run after the task that requires finalization, regardless of whether the task succeeds or fails.
task a { ... }
task b { ... }
a.finalizedBy b