Gradle

Avoid broad commands unless necessary:

./gradlew build
./gradlew test
./gradlew check

Wrapper Pattern

#!/usr/bin/env bash
set -euo pipefail

LOG_DIR=".agent-logs"
LOG_FILE="$LOG_DIR/gradle.log"
mkdir -p "$LOG_DIR"

set +e
./gradlew -q --console=plain --warning-mode=none "$@" >"$LOG_FILE" 2>&1
EXIT_CODE=$?
set -e

echo "Exit code: $EXIT_CODE"

if [ "$EXIT_CODE" -eq 0 ]; then
  echo "Status: SUCCESS"
  grep -E "^(BUILD SUCCESSFUL|[0-9]+ actionable tasks:)" "$LOG_FILE" | tail -n 2 || true
  exit 0
fi

echo "Status: FAILURE"
grep -E "^Execution failed for task " "$LOG_FILE" | head -n 10 || true
echo
tail -n 80 "$LOG_FILE"
echo
echo "Full log: $LOG_FILE"

exit "$EXIT_CODE"

Return Format

Success

Exit code: 0
Status: SUCCESS
BUILD SUCCESSFUL in 4s
6 actionable tasks: 2 executed, 4 up-to-date

Failure

Exit code: 1
Status: FAILURE
Execution failed for task ':app:test'.

...last 80 lines...

Full log: .agent-logs/gradle.log

Debugging Order

1. Run the narrowest task
2. Read the summary
3. Read the short tail on failure
4. Open the full log only if needed
5. Inspect test XML/reports when that is more useful than console output

Common Artifacts

build/test-results/test/
build/reports/tests/test/
build/reports/problems/

Avoid

• streaming full Gradle output into model context
• using --info, --debug, or --stacktrace by default
• rerunning build repeatedly during tight loops
• pasting full stack traces unless specifically needed

Rule of Thumb

Capture everything, return only the minimum needed to decide the next step.