DevOps / Gradle8 Interview Questions
Explain the execution flow of a Gradle build from invocation to completion?
Running ./gradlew build moves through the same three fixed phases every time, regardless of project size.
flowchart TD
A[gradlew build invoked] --> B[Daemon started or reused]
B --> C[Initialization: read settings.gradle, create Project instances]
C --> D[Configuration: run every project's build.gradle, register tasks]
D --> E[Task graph assembled from requested tasks and their dependsOn chains]
E --> F{Configuration cache hit?}
F -- Yes --> G[Skip re-running scripts, reuse stored task graph]
F -- No --> H[Full configuration phase runs, result cached for next time]
G --> I[Execution: run up-to-date check per task]
H --> I
I --> J{Task inputs/outputs unchanged?}
J -- Yes --> K[Skip task, mark UP-TO-DATE]
J -- No --> L[Execute task action, e.g. compile/test]
K --> M[Build completes]
L --> M
The key structural point for interviews: configuration always evaluates the build scripts to know what could run, while execution decides what actually needs to run — conflating the two is the most common source of confusion about why a piece of build-script code executed even though the task it configured never ran.
What does the configuration phase determine, as distinct from the execution phase?
What happens to a task whose inputs and outputs are unchanged during execution?
More Related questions...
