build: revert gradle heap cap, keep CI builds unconstrained

The 768m heap cap broke GitHub Actions (KSP OutOfMemoryError: Metaspace) because CI runners read the same gradle.properties. Restore -Xmx6g for CI; the 2GB local server should pass a one-off -Dorg.gradle.jvmargs instead.
This commit is contained in:
mckero committed 2026-08-03 10:49:59 +00:00
1 parent 929f652b8e
commit 8a920acead
1 file changed
+3 -4
+3 -4
View File
@@ -1,6 +1,5 @@
# Configure your build environment: http://www.gradle.org/docs/current/userguide/build_environment.html # Configure your build environment: http://www.gradle.org/docs/current/userguide/build_environment.html
org.gradle.caching=true org.gradle.caching=true
# NOTE: lowered from -Xmx6g for the 2GB build server; heavy release builds run on GitHub Actions org.gradle.jvmargs=-Xmx6g -XX:MaxMetaspaceSize=1g -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
org.gradle.jvmargs=-Xmx768m -XX:MaxMetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8 org.gradle.parallel=true
org.gradle.parallel=false org.gradle.workers.max=4
org.gradle.workers.max=1