ci: cache Maven repository explicitly for both Java jobs

The built-in cache: maven in setup-java@v4 does not reliably work on self-hosted act runners. Replace with an explicit actions/cache@v4 on ~/.m2/repository keyed on pom.xml hash. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ci: cache node_modules and Playwright browser binary
2026-03-17 22:06:35 +01:00 · 2026-03-17 22:03:40 +01:00
1 changed files with 58 additions and 8 deletions
--- a/.gitea/workflows/ci.yml
+++ b/.gitea/workflows/ci.yml
@@ -16,17 +16,36 @@ jobs:
      - uses: actions/setup-node@v4
        with:
          node-version: 20
-          cache: npm
-          cache-dependency-path: frontend/package-lock.json
+
+      - name: Cache node_modules
+        id: node-modules-cache
+        uses: actions/cache@v4
+        with:
+          path: frontend/node_modules
+          key: node-modules-${{ hashFiles('frontend/package-lock.json') }}

      - name: Install dependencies
+        if: steps.node-modules-cache.outputs.cache-hit != 'true'
        run: npm ci
        working-directory: frontend

-      - name: Install Playwright Chromium (used by vitest browser mode)
+      - name: Cache Playwright browsers
+        id: playwright-cache
+        uses: actions/cache@v4
+        with:
+          path: ~/.cache/ms-playwright
+          key: playwright-chromium-${{ hashFiles('frontend/package-lock.json') }}
+
+      - name: Install Playwright Chromium + system deps
+        if: steps.playwright-cache.outputs.cache-hit != 'true'
        run: npx playwright install chromium --with-deps
        working-directory: frontend

+      - name: Install Playwright system deps (browser binary already cached)
+        if: steps.playwright-cache.outputs.cache-hit == 'true'
+        run: npx playwright install-deps chromium
+        working-directory: frontend
+
      - name: Run unit and component tests
        run: npm test
        working-directory: frontend
@@ -50,7 +69,13 @@ jobs:
        with:
          java-version: '21'
          distribution: temurin
-          cache: maven
+
+      - name: Cache Maven repository
+        uses: actions/cache@v4
+        with:
+          path: ~/.m2/repository
+          key: maven-${{ hashFiles('backend/pom.xml') }}
+          restore-keys: maven-

      - name: Run backend tests
        run: |
@@ -99,7 +124,13 @@ jobs:
        with:
          java-version: '21'
          distribution: temurin
-          cache: maven
+
+      - name: Cache Maven repository
+        uses: actions/cache@v4
+        with:
+          path: ~/.m2/repository
+          key: maven-${{ hashFiles('backend/pom.xml') }}
+          restore-keys: maven-

      - name: Build backend (skip tests — covered by separate Java test job)
        run: |
@@ -131,17 +162,36 @@ jobs:
      - uses: actions/setup-node@v4
        with:
          node-version: 20
-          cache: npm
-          cache-dependency-path: frontend/package-lock.json
+
+      - name: Cache node_modules
+        id: node-modules-cache
+        uses: actions/cache@v4
+        with:
+          path: frontend/node_modules
+          key: node-modules-${{ hashFiles('frontend/package-lock.json') }}

      - name: Install frontend dependencies
+        if: steps.node-modules-cache.outputs.cache-hit != 'true'
        run: npm ci
        working-directory: frontend

-      - name: Install Playwright Chromium
+      - name: Cache Playwright browsers
+        id: playwright-cache
+        uses: actions/cache@v4
+        with:
+          path: ~/.cache/ms-playwright
+          key: playwright-chromium-${{ hashFiles('frontend/package-lock.json') }}
+
+      - name: Install Playwright Chromium + system deps
+        if: steps.playwright-cache.outputs.cache-hit != 'true'
        run: npx playwright install chromium --with-deps
        working-directory: frontend

+      - name: Install Playwright system deps (browser binary already cached)
+        if: steps.playwright-cache.outputs.cache-hit == 'true'
+        run: npx playwright install-deps chromium
+        working-directory: frontend
+
      # ── Tests ────────────────────────────────────────────────────────────────
      - name: Run E2E tests
        run: npm run test:e2e
Author	SHA1	Message	Date
Marcel	553fa8a4b9	ci: cache Maven repository explicitly for both Java jobs Some checks failed CI / Backend Unit Tests (push) Has been cancelled Details CI / E2E Tests (push) Has been cancelled Details CI / Unit & Component Tests (push) Has been cancelled Details CI / Unit & Component Tests (pull_request) Has been cancelled Details CI / Backend Unit Tests (pull_request) Has been cancelled Details CI / E2E Tests (pull_request) Has been cancelled Details The built-in cache: maven in setup-java@v4 does not reliably work on self-hosted act runners. Replace with an explicit actions/cache@v4 on ~/.m2/repository keyed on pom.xml hash. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-17 22:06:35 +01:00
Marcel	409e70078c	ci: cache node_modules and Playwright browser binary Some checks failed CI / Unit & Component Tests (push) Has been cancelled Details CI / Backend Unit Tests (push) Has been cancelled Details CI / E2E Tests (push) Has been cancelled Details node_modules and the Playwright Chromium binary were downloaded fresh on every run, making setup account for ~99% of pipeline runtime. - Cache frontend/node_modules keyed on package-lock.json hash - Cache ~/.cache/ms-playwright keyed on package-lock.json hash - On cache hit: skip npm ci and browser download, only reinstall system deps (install-deps) which is much faster than a full install Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-17 22:03:40 +01:00