ci: cut the pipeline from 13 minutes to a single fast build
CI / build (push) Successful in 1m53s

The production Wasm optimizer dominated the old run (about 10 of 13
minutes). Main/PR builds now produce the development Wasm bundle, while
the optimized bundle and desktop fat jar are built only for release tags.

Merge test and build into one job so a checkout and a Gradle run are not
repeated, and bake the Gradle dependency cache plus the Android SDK into
the CI image. Raise the version of the image to 2.
This commit is contained in:
TapTap committed 2026-11-14 19:51:11 +00:00
1 parent 3281e46104
commit 7fb41b5ad4
5 files changed
+60 -29

No files matched your search

+7 -7
View File
@@ -104,19 +104,19 @@ Adding a song makes it a permanent seed, so it is always eligible in future radi
## CI and releases
`.gitea/workflows/ci.yaml` runs on Gitea Actions using `gitea.tap-tap.win/taptap/audiomanager-client-ci:1`:
`.gitea/workflows/ci.yaml` runs on Gitea Actions using `gitea.tap-tap.win/taptap/audiomanager-client-ci:2`. The image has the Android SDK installed and a warmed Gradle dependency cache, so jobs do not download either on every run.
1. `desktopTest` — shared API/cache tests.
2. Build Android APK, desktop fat jar and Wasm bundle.
3. Upload artifacts.
4. On a `v*` tag, attach the three artifacts to the Gitea release.
- **main / PR:** run `desktopTest`, build the Android APK and the *development* Wasm bundle. The optimized Wasm build is CPU-bound and reserved for releases.
- **`v*` tag:** additionally build the desktop fat jar and the optimized Wasm bundle, then attach all three to the Gitea release.
Rebuild the CI image after changing `ci/Dockerfile`:
Rebuild the CI image after changing `ci/Dockerfile` or dependency versions:
```bash
scripts/build-ci-image.sh 2
scripts/build-ci-image.sh 3
```
The image build performs one warm-up compile (`desktopTest`, `assembleDebug`, `compileKotlinWasmJs`) and then removes the sources, keeping only `/root/.gradle`.
## Known limitations
- Android playback runs inside the app process; a foreground `MediaSessionService` with a notification and lock-screen controls is the next step.