Skip to content

Commit d2a26dc

Browse files
committed
ci(e2e): set up JDK 17 unconditionally (Maestro needs Java to run)
Run 25748105365 confirmed the APK cache hit works — but the Android job failed with: ERROR: Java 17 or higher is required. Please update Java, then try again. Maestro CLI is a JVM app and needs Java 17+ to launch. I had gated the JDK setup step on cache miss (thinking it was only needed for gradle), which means on the very first cache hit there's no Java for Maestro. Remove that gate. Note: this workflow file change invalidates the source hash, so the next run is back to cold cache. The run after that will be the actual warm- cache demonstration.
1 parent a66a391 commit d2a26dc

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

.github/workflows/mobile-e2e.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -218,7 +218,9 @@ jobs:
218218
| jq '{id, email_addresses: [.email_addresses[].email_address], password_enabled, banned, locked}'
219219
220220
- name: Set up JDK 17
221-
if: steps.apk-cache.outputs.cache-hit != 'true'
221+
# Always run, not just on cache miss: Maestro itself requires Java 17+
222+
# to launch (the maestro CLI is a JVM app). When the APK cache hits
223+
# and we skip gradle, we still need Java for the Maestro test step.
222224
uses: actions/setup-java@v4
223225
with:
224226
distribution: temurin

0 commit comments

Comments
 (0)