ci: drop the Wasm build from the pipeline
CI / build (push) Successful in 2m57s
CI / play (push) Skipped

It is CPU-bound and dominates the runtime. The target stays available for
local builds with :composeApp:wasmJsBrowserDistribution.
This commit is contained in:
TapTap committed 2026-11-18 19:26:04 +00:00
1 parent e28e95fa2b
commit 14e5b9d982
2 files changed
+8 -11

No files matched your search

+6 -6
View File
@@ -133,7 +133,7 @@ gradle :composeApp:run
# Desktop fat jar
gradle :composeApp:packageUberJarForCurrentOS
# Web bundle
# Web bundle (local only, not built by CI)
gradle :composeApp:wasmJsBrowserDistribution
# composeApp/build/dist/wasmJs/productionExecutable
```
@@ -250,11 +250,11 @@ radio and visible in the song list.
`gitea.tap-tap.win/taptap/audiomanager-client-ci:3`. The image has the Android
SDK, Node, Yarn and a warmed Gradle dependency cache.
- **main / PR:** run `desktopTest`, build the Android APK and the *development*
Wasm bundle.
- **`v*` tag:** additionally build the desktop fat jar and the optimized Wasm
bundle, attach the artifacts to the Gitea release, and publish the AAB to Play
internal testing.
- **main / PR:** run `desktopTest` and build the Android APK.
- **`v*` tag:** additionally build the desktop fat jar, attach the artifacts to
the Gitea release, and publish the AAB to Play internal testing.
- The Wasm target stays in the project for local builds but is **not** part of
CI; compiling it dominates the pipeline runtime.
Rebuild the CI image after changing `ci/Dockerfile` or dependency versions: