CI: build Android (assembleDebug) on merge to master #57
Notifications
Due Date
No due date set.
Blocks
Depends on
#58 Add Deploy Android workflow_dispatch button (signed AAB)
ai_ml_operations/chat_web_app
#9 Android CI/deploy support: JDK 17 + SDK 35 on runner, keystore secrets layout
ai_ml_operations/server-infra
Reference: ai_ml_operations/chat_web_app#57
Reference in New Issue
Block a user
Summary
Add a Gitea Actions workflow that builds the Capacitor Android app on every push/merge to
master, so we know the native shell still compiles before we clean up / prune Android-related files and keep regressions from landing silently.Today: Unit Tests + Deploy Beta run on
master; no Android/Gradle step exists. Capacitor project lives atllm-fe/android/(appIdcom.aimloperations.chat, Hesychia).Infra half (runner JDK/SDK): server-infra#9.
Follow-on: manual Deploy Android button — #58.
Current state
unit-tests.ymlmasterdeploy-beta.ymlmasterdeploy-prod.ymlworkflow_dispatchLocal build path already documented:
Work
1. New workflow
.gitea/workflows/android-build.ymlAndroid Buildpushtomaster(optional: alsopull_request→master)self-hostedactions/checkout@v4npm ciinllm-fenpm run build:mobilecd android && ./gradlew assembleDebug --no-daemonapp/build/outputs/apk/debug/app-debug.apkas artifactPrefer unsigned debug here — no keystore required. Keeps master gate cheap and green without Play secrets.
2. Docs
README.mdCI table +llm-fe/ANDROID.mdto list the new workflow3. Out of scope
bundleRelease/ Play upload → Add Deploy Android workflow_dispatch button (signed AAB) (#58)deploy.sh/ beta/prod webrootsCoordination
ANDROID_HOME) — server-infra#9Acceptance criteria
masterruns an Android build job that completesassembleDebugReferences
llm-fe/package.json(build:mobile),llm-fe/android/.gitea/workflows/unit-tests.yml,deploy-prod.yml