gradle --continue: Report Every Failure
gradle --continue does not stop at the first failing task; it runs every task whose dependencies still succeeded and reports all failures together.
Default Gradle aborts on the first failure. In CI you usually want the full picture, so --continue surfaces every broken module in one run.
What it does
With --continue, a task failure does not abort the build. Gradle still skips tasks that depended on the failed task, but it runs everything else and then fails the build at the end, listing all collected failures. This is ideal for getting a complete report from a multi-module check.
Common usage
./gradlew check --continue
./gradlew build --continue
./gradlew test --continue --console=plainFlags
| Flag | What it does |
|---|---|
| --continue | Keep running after a task fails |
| --console=plain | Cleaner failure summary in CI logs |
| -S / --full-stacktrace | Full stacktraces for each failure |
In CI
Pair --continue with check so one failing module does not mask failures in others; the job then reports every problem in a single run, cutting the fix-push-wait cycle. Publish all reports under build/reports as artifacts since several may have failed.
Common errors in CI
The build still ends with "BUILD FAILED" and a list like "N actionable tasks ... 2 failed"; that is expected, --continue does not make failures pass. Tasks that depended on a failed task are skipped, so a downstream "task was not executed" is a consequence, not a separate error.