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

+2 -5
View File
@@ -45,15 +45,13 @@ jobs:
:composeApp:desktopTest \
:composeApp:assembleDebug \
:composeApp:packageUberJarForCurrentOS \
:composeApp:wasmJsBrowserDistribution \
--console=plain
else
# The optimized Wasm build is CPU-bound and slow; main/PR builds
# only need to prove the web target compiles and bundles.
# The Wasm target is kept for local builds but is not part of CI:
# it is CPU-bound and dominates the pipeline runtime.
gradle \
:composeApp:desktopTest \
:composeApp:assembleDebug \
:composeApp:wasmJsBrowserDevelopmentExecutableDistribution \
--console=plain
fi
@@ -64,7 +62,6 @@ jobs:
cp composeApp/build/outputs/apk/debug/composeApp-debug.apk dist/AudioManager.apk
if [[ "$GITHUB_REF" == refs/tags/* ]]; then
cp composeApp/build/compose/jars/*.jar dist/AudioManager-desktop.jar
(cd composeApp/build/dist/wasmJs/productionExecutable && zip -qr "$GITHUB_WORKSPACE/dist/AudioManager-web.zip" .)
fi
- name: Publish release assets