ehealthsolutions/element-x-android
3
0
Fork 0
mirror of https://github.com/Novaloop-AG/element-x-android.git synced 2026-10-31 08:15:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: record why the Gradle heap is reduced

Browse Source
This commit is contained in:
Joël Poyet
2026-08-04 12:55:48 +02:00
parent 409a1e5b90
commit 8c4ef9264b
7 changed files with 49 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/build.yml
+7 -4
View File
@@ -15,10 +15,13 @@ permissions:
# Enrich gradle.properties for CI/CD
env:
# Sized for the self-hosted incus containers, matching
# healthchat-release-playstore.yml. Upstream's -Xmx8g with a 4 GB Kotlin daemon is
# sized for GitHub's hosted VMs; here the daemon gets SIGKILLed mid-build and Gradle
# reports "the daemon has disappeared" with no OutOfMemoryError and no heap dump.
# Reduced from upstream's -Xmx8g / 4 GB Kotlin daemon for the self-hosted runners.
# Each incus container reports 48 GiB and 8 cores, so a single build has ample room —
# but the containers are oversubscribed against their host, and two concurrent heavy
# Gradle jobs get their daemons SIGKILLed ("the daemon has disappeared", no
# OutOfMemoryError, no heap dump). Running the same job alone succeeds. Lower heaps
# make two builds likelier to coexist; the real fix is sizing the containers to the
# host. See the "Report runner capacity" step.
GRADLE_OPTS: -Dorg.gradle.jvmargs=-Xmx6g -XX:MaxMetaspaceSize=768m -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError -XX:+UseG1GC -Dkotlin.daemon.jvm.options=-Xmx2g
CI_GRADLE_ARG_PROPERTIES: --stacktrace -Dsonar.gradle.skipCompile=true --no-configuration-cache
.github/workflows/build_enterprise.yml
+7 -4
View File
@@ -15,10 +15,13 @@ permissions:
# Enrich gradle.properties for CI/CD
env:
# Sized for the self-hosted incus containers, matching
# healthchat-release-playstore.yml. Upstream's -Xmx8g with a 4 GB Kotlin daemon is
# sized for GitHub's hosted VMs; here the daemon gets SIGKILLed mid-build and Gradle
# reports "the daemon has disappeared" with no OutOfMemoryError and no heap dump.
# Reduced from upstream's -Xmx8g / 4 GB Kotlin daemon for the self-hosted runners.
# Each incus container reports 48 GiB and 8 cores, so a single build has ample room —
# but the containers are oversubscribed against their host, and two concurrent heavy
# Gradle jobs get their daemons SIGKILLed ("the daemon has disappeared", no
# OutOfMemoryError, no heap dump). Running the same job alone succeeds. Lower heaps
# make two builds likelier to coexist; the real fix is sizing the containers to the
# host. See the "Report runner capacity" step.
GRADLE_OPTS: -Dorg.gradle.jvmargs=-Xmx6g -XX:MaxMetaspaceSize=768m -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError -XX:+UseG1GC -Dkotlin.daemon.jvm.options=-Xmx2g
CI_GRADLE_ARG_PROPERTIES: --stacktrace -Dsonar.gradle.skipCompile=true --no-configuration-cache
.github/workflows/maestro-local.yml
+7 -4
View File
@@ -13,10 +13,13 @@ permissions:
# Enrich gradle.properties for CI/CD
env:
# Sized for the self-hosted incus containers, matching
# healthchat-release-playstore.yml. Upstream's -Xmx8g with a 4 GB Kotlin daemon is
# sized for GitHub's hosted VMs; here the daemon gets SIGKILLed mid-build and Gradle
# reports "the daemon has disappeared" with no OutOfMemoryError and no heap dump.
# Reduced from upstream's -Xmx8g / 4 GB Kotlin daemon for the self-hosted runners.
# Each incus container reports 48 GiB and 8 cores, so a single build has ample room —
# but the containers are oversubscribed against their host, and two concurrent heavy
# Gradle jobs get their daemons SIGKILLed ("the daemon has disappeared", no
# OutOfMemoryError, no heap dump). Running the same job alone succeeds. Lower heaps
# make two builds likelier to coexist; the real fix is sizing the containers to the
# host. See the "Report runner capacity" step.
GRADLE_OPTS: -Dorg.gradle.jvmargs=-Xmx6g -XX:MaxMetaspaceSize=768m -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError -XX:+UseG1GC -Dkotlin.daemon.jvm.options=-Xmx2g
CI_GRADLE_ARG_PROPERTIES: --stacktrace --no-daemon -Dsonar.gradle.skipCompile=true --no-configuration-cache
ARCH: x86_64
.github/workflows/quality.yml
+7 -4
View File
@@ -15,10 +15,13 @@ permissions:
# Enrich gradle.properties for CI/CD
env:
# Sized for the self-hosted incus containers, matching
# healthchat-release-playstore.yml. Upstream's -Xmx8g with a 4 GB Kotlin daemon is
# sized for GitHub's hosted VMs; here the daemon gets SIGKILLed mid-build and Gradle
# reports "the daemon has disappeared" with no OutOfMemoryError and no heap dump.
# Reduced from upstream's -Xmx8g / 4 GB Kotlin daemon for the self-hosted runners.
# Each incus container reports 48 GiB and 8 cores, so a single build has ample room —
# but the containers are oversubscribed against their host, and two concurrent heavy
# Gradle jobs get their daemons SIGKILLed ("the daemon has disappeared", no
# OutOfMemoryError, no heap dump). Running the same job alone succeeds. Lower heaps
# make two builds likelier to coexist; the real fix is sizing the containers to the
# host. See the "Report runner capacity" step.
GRADLE_OPTS: -Dorg.gradle.jvmargs=-Xmx6g -XX:MaxMetaspaceSize=768m -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError -XX:+UseG1GC -Dkotlin.daemon.jvm.options=-Xmx2g
CI_GRADLE_ARG_PROPERTIES: --stacktrace --no-daemon -Dsonar.gradle.skipCompile=true --no-configuration-cache
.github/workflows/recordScreenshots.yml
+7 -4
View File
@@ -13,10 +13,13 @@ permissions:
# Enrich gradle.properties for CI/CD
env:
# Sized for the self-hosted incus containers, matching
# healthchat-release-playstore.yml. Upstream's -Xmx8g with a 4 GB Kotlin daemon is
# sized for GitHub's hosted VMs; here the daemon gets SIGKILLed mid-build and Gradle
# reports "the daemon has disappeared" with no OutOfMemoryError and no heap dump.
# Reduced from upstream's -Xmx8g / 4 GB Kotlin daemon for the self-hosted runners.
# Each incus container reports 48 GiB and 8 cores, so a single build has ample room —
# but the containers are oversubscribed against their host, and two concurrent heavy
# Gradle jobs get their daemons SIGKILLed ("the daemon has disappeared", no
# OutOfMemoryError, no heap dump). Running the same job alone succeeds. Lower heaps
# make two builds likelier to coexist; the real fix is sizing the containers to the
# host. See the "Report runner capacity" step.
GRADLE_OPTS: -Dorg.gradle.jvmargs=-Xmx6g -XX:MaxMetaspaceSize=768m -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError -XX:+UseG1GC -Dkotlin.daemon.jvm.options=-Xmx2g -Dsonar.gradle.skipCompile=true
CI_GRADLE_ARG_PROPERTIES: --no-configuration-cache
.github/workflows/sonar.yml
+7 -4
View File
@@ -15,10 +15,13 @@ permissions:
# Enrich gradle.properties for CI/CD
env:
# Sized for the self-hosted incus containers, matching
# healthchat-release-playstore.yml. Upstream's -Xmx8g with a 4 GB Kotlin daemon is
# sized for GitHub's hosted VMs; here the daemon gets SIGKILLed mid-build and Gradle
# reports "the daemon has disappeared" with no OutOfMemoryError and no heap dump.
# Reduced from upstream's -Xmx8g / 4 GB Kotlin daemon for the self-hosted runners.
# Each incus container reports 48 GiB and 8 cores, so a single build has ample room —
# but the containers are oversubscribed against their host, and two concurrent heavy
# Gradle jobs get their daemons SIGKILLed ("the daemon has disappeared", no
# OutOfMemoryError, no heap dump). Running the same job alone succeeds. Lower heaps
# make two builds likelier to coexist; the real fix is sizing the containers to the
# host. See the "Report runner capacity" step.
GRADLE_OPTS: -Dorg.gradle.jvmargs=-Xmx6g -XX:MaxMetaspaceSize=768m -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError -XX:+UseG1GC -Dkotlin.daemon.jvm.options=-Xmx2g
CI_GRADLE_ARG_PROPERTIES: --stacktrace --warn -Dsonar.gradle.skipCompile=true --no-configuration-cache
GROUP: ${{ format('sonar-{0}', github.ref) }}
.github/workflows/tests.yml
+7 -4
View File
@@ -15,10 +15,13 @@ permissions:
# Enrich gradle.properties for CI/CD
env:
# Sized for the self-hosted incus containers, matching
# healthchat-release-playstore.yml. Upstream's -Xmx8g with a 4 GB Kotlin daemon is
# sized for GitHub's hosted VMs; here the daemon gets SIGKILLed mid-build and Gradle
# reports "the daemon has disappeared" with no OutOfMemoryError and no heap dump.
# Reduced from upstream's -Xmx8g / 4 GB Kotlin daemon for the self-hosted runners.
# Each incus container reports 48 GiB and 8 cores, so a single build has ample room —
# but the containers are oversubscribed against their host, and two concurrent heavy
# Gradle jobs get their daemons SIGKILLed ("the daemon has disappeared", no
# OutOfMemoryError, no heap dump). Running the same job alone succeeds. Lower heaps
# make two builds likelier to coexist; the real fix is sizing the containers to the
# host. See the "Report runner capacity" step.
GRADLE_OPTS: -Dorg.gradle.jvmargs="-Xmx6g -XX:MaxMetaspaceSize=768m -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError" -Dkotlin.daemon.jvm.options=-Xmx2g -XX:+UseG1GC
CI_GRADLE_ARG_PROPERTIES: --stacktrace --no-daemon -Dsonar.gradle.skipCompile=true --no-configuration-cache