Xeewy/TravelMate
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: Increase Gradle JVM memory allocation in Android deployment workflow to 3072m.
Some checks failed
Deploy Flutter to Firebase / deploy-android (push) Failing after 22m42s
Details

Browse Source
This commit is contained in:
Van Leemput Dayron
2025-12-13 11:47:08 +01:00
parent 329708fe6c
commit c63124b16b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.gitea/workflows/deploy-android.yaml
View File

@@ -49,7 +49,7 @@ jobs:
ANDROID_KEYSTORE_BASE64: ${{ secrets.ANDROID_KEYSTORE_BASE64 }} ANDROID_KEYSTORE_BASE64: ${{ secrets.ANDROID_KEYSTORE_BASE64 }}
FIREBASE_ANDROID_APP_ID: ${{ secrets.FIREBASE_ANDROID_APP_ID }} FIREBASE_ANDROID_APP_ID: ${{ secrets.FIREBASE_ANDROID_APP_ID }}
# --- C'EST ICI LA CORRECTION CRITIQUE POUR LA MÉMOIRE --- # --- C'EST ICI LA CORRECTION CRITIQUE POUR LA MÉMOIRE ---
GRADLE_OPTS: "-Dorg.gradle.daemon=false -Dorg.gradle.jvmargs=-Xmx1536m" GRADLE_OPTS: "-Dorg.gradle.daemon=false -Dorg.gradle.jvmargs=-Xmx3072m"
run: | run: |
bundle install bundle install
bundle exec fastlane deploy_firebase bundle exec fastlane deploy_firebase