domains / families / devops / gradle-run

gradle-run

separate

Use when planning to execute Gradle through `gradle`, `./gradlew`, or a custom `gradlew*` wrapper script, or diagnosing a Gradle build, recovering a workflow's status, compact workflow ledger, repeated failure fingerprint, check, test, lint, warning, or failure even when no new Gradle run is appropriate.

When to use

• executing Gradle through gradle, ./gradlew, or custom wrapper
• diagnosing a Gradle build
• recovering a workflow's status
• managing compact workflow ledger
• handling repeated failure fingerprint
• running check, test, lint, warning, or failure tasks

When not to use

• streaming, tee, pasting, or reopening full build logs
• running Gradle directly as a fallback if python3 or scripts/gradle_run.py is unavailable
• combining create, run, or finish with other shell commands, pipes, or conditionals
• inferring completion from PID, rerun, cleanup, finish, or process termination when status is uncertain

Skill page

Source