ci(release): serialize play before the fdroid_reference chain
All checks were successful
ci / analyze (push) Successful in 3m17s
ci / test-commons-core (push) Successful in 1m26s
ci / test-app-seeds (push) Successful in 11m1s

A tag push started play (AAB → Play) and fdroid_reference_armeabi_v7a at
the same instant; two heavy Android builds on the shared runner
(capacity:2) OOM-killed play's Gradle daemon ('daemon disappeared') deep
in bundleRelease. Chain the fdroid references after play with needs:play
+ if:always() so only one Android build runs at a time. if:always() keeps
the fdroid chain independent of play's result (still runs when play fails
or, on workflow_dispatch, is skipped).
This commit is contained in:
vjrj 2026-07-21 23:57:38 +02:00
parent 538b28e5d2
commit 841cb9aaec

View file

@ -111,6 +111,13 @@ jobs:
run: rm -f android/key.properties "$GITHUB_WORKSPACE/tane-upload.jks"
fdroid_reference_armeabi_v7a:
# Serialize after play so two heavy Android builds never run concurrently on
# the shared host (capacity:2) — that contention OOM-killed play's Gradle
# daemon. `if: always()` keeps the fdroid chain independent of play's result
# (runs after play whether it succeeded, failed, or — on workflow_dispatch —
# was skipped).
needs: play
if: ${{ always() }}
runs-on: docker
container:
image: registry.gitlab.com/fdroid/fdroidserver:buildserver-trixie