DevOps / Gradle8 Interview Questions
Explain the lifecycle of a Gradle task?
A task moves through creation, configuration, and (conditionally) execution, and understanding where each step happens explains a lot of otherwise-confusing Gradle behavior.
flowchart TD
A[tasks.register called during script evaluation] --> B[Task instance created lazily — not yet fully configured]
B --> C{Task actually needed for this build invocation?}
C -- No --> D[Task never configured further, no action runs]
C -- Yes --> E[Configuration block runs: inputs/outputs/dependsOn set up]
E --> F[Task added to the execution graph]
F --> G{Up-to-date check passes?}
G -- Yes --> H[Task SKIPPED, marked UP-TO-DATE]
G -- No --> I[doFirst actions run]
I --> J[Main task action runs]
J --> K[doLast actions run]
K --> L[Task marked complete]
The lazy registration step (via tasks.register) is what lets Gradle skip configuring tasks nobody actually requested, which matters a lot in large builds with hundreds of possible tasks where only a handful are relevant to any given invocation.
What does lazy registration (tasks.register) allow Gradle to skip for tasks not actually needed?
In what order do a task's actions run once it's determined to actually execute?
More Related questions...
