[skip ci] Remove CI-specific Gradle config

Newer versions of gradle-build-action allows the daemon to persist across build steps
This commit is contained in:
arkon 2022-06-11 11:38:16 -04:00
parent e15a867106
commit 1e64542f14
4 changed files with 1 additions and 16 deletions

View file

@ -1,5 +0,0 @@
org.gradle.daemon=false
org.gradle.jvmargs=-Xmx5120m
org.gradle.workers.max=2
kotlin.incremental=false

View file

@ -29,11 +29,6 @@ jobs:
java-version: 11
distribution: adopt
- name: Copy CI gradle.properties
run: |
mkdir -p ~/.gradle
cp .github/runner-files/ci-gradle.properties ~/.gradle/gradle.properties
- name: Build app and run unit tests
uses: gradle/gradle-command-action@v2
with:

View file

@ -30,11 +30,6 @@ jobs:
java-version: 11
distribution: adopt
- name: Copy CI gradle.properties
run: |
mkdir -p ~/.gradle
cp .github/runner-files/ci-gradle.properties ~/.gradle/gradle.properties
- name: Build app and run unit tests
uses: gradle/gradle-command-action@v2
with:

View file

@ -11,7 +11,7 @@
# The setting is particularly useful for tweaking memory settings.
# Default value: -Xmx10248m -XX:MaxPermSize=256m
# org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
org.gradle.jvmargs=-Xmx4096m
org.gradle.jvmargs=-Xmx5120m
# When configured, Gradle will run in incubating parallel mode.
# This option should only be used with decoupled projects. More details, visit