Increase mvn memory within github action (#3689)

* Switch to 6g ram
matsim-org · Jan 25, 2025 · 31ed6db · 31ed6db
1 parent 90a3fb3
commit 31ed6db
Show file tree

Hide file tree

Showing 6 changed files with 6 additions and 6 deletions.
diff --git a/.github/workflows/code-coverage.yaml b/.github/workflows/code-coverage.yaml
@@ -31,4 +31,4 @@ jobs:
           files: ./matsim/target/site/jacoco/jacoco.xml
 
     env:
-      MAVEN_OPTS: -Xmx2g
+      MAVEN_OPTS: -Xmx6g
diff --git a/.github/workflows/deploy-on-pr-merge.yaml b/.github/workflows/deploy-on-pr-merge.yaml
@@ -49,4 +49,4 @@ jobs:
         uses: advanced-security/maven-dependency-submission-action@v4
 
     env:
-      MAVEN_OPTS: -Xmx2g
+      MAVEN_OPTS: -Xmx6g
diff --git a/.github/workflows/deploy-on-release-created.yaml b/.github/workflows/deploy-on-release-created.yaml
@@ -44,4 +44,4 @@ jobs:
           file: matsim/target/matsim-${{ github.event.release.tag_name }}-release.zip
           tag: ${{ github.event.release.tag_name }}
     env:
-      MAVEN_OPTS: -Xmx2g
+      MAVEN_OPTS: -Xmx6g
diff --git a/.github/workflows/deploy-weekly.yaml b/.github/workflows/deploy-weekly.yaml
@@ -39,4 +39,4 @@ jobs:
           MAVEN_PASSWORD: ${{ secrets.REPOMATSIM_TOKEN }}
 
     env:
-      MAVEN_OPTS: -Xmx2g
+      MAVEN_OPTS: -Xmx6g
diff --git a/.github/workflows/full-integration.yaml b/.github/workflows/full-integration.yaml
@@ -38,7 +38,7 @@ jobs:
         run: mvn verify -P release --batch-mode --fail-at-end -D'maven.test.redirectTestOutputToFile' -D'matsim.preferLocalDtds=true'
 
     env:
-      MAVEN_OPTS: -Xmx2g
+      MAVEN_OPTS: -Xmx6
 
   verify-full-integration-successful:
     # always() - to ensure this job is executed (regardless of the status of the previous job)

diff --git a/.github/workflows/verify-push.yaml b/.github/workflows/verify-push.yaml
@@ -101,7 +101,7 @@ jobs:
         working-directory: ${{matrix.module}}
 
     env:
-      MAVEN_OPTS: -Xmx2g
+      MAVEN_OPTS: -Xmx6g
 
   verify-all-jobs-successful:
     # always() - to ensure this job is executed (regardless of the status of the previous job)