ci: re-enable actions cache now that the runner serves it #6

Merged
developer merged 1 commits from feature/enable-actions-cache into development 2026-05-15 05:46:57 +00:00
5 changed files with 10 additions and 24 deletions
+3 -7
View File
@@ -40,8 +40,7 @@ jobs:
uses: actions/setup-go@v5 uses: actions/setup-go@v5
with: with:
go-version-file: go.work go-version-file: go.work
# See go-unit.yaml for why `cache: true` is disabled. cache: true
cache: false
- name: Set up pnpm - name: Set up pnpm
uses: pnpm/action-setup@v4 uses: pnpm/action-setup@v4
@@ -52,11 +51,8 @@ jobs:
uses: actions/setup-node@v4 uses: actions/setup-node@v4
with: with:
node-version: 22 node-version: 22
# `cache: pnpm` pushes the pnpm store through the Gitea cache: pnpm
# Actions cache service which is currently unreachable cache-dependency-path: ui/pnpm-lock.yaml
# (192.168.0.222:43513 ETIMEDOUT). In host-mode the real
# store lives in ~/.local/share/pnpm and persists between
# jobs without any action plumbing.
- name: Install UI dependencies - name: Install UI dependencies
working-directory: ui working-directory: ui
+1 -7
View File
@@ -46,13 +46,7 @@ jobs:
uses: actions/setup-go@v5 uses: actions/setup-go@v5
with: with:
go-version-file: go.work go-version-file: go.work
# `cache: true` here pushes/pulls archives through the Gitea cache: true
# Actions cache service at 192.168.0.222:43513. That endpoint
# currently does not answer, and the action wastes minutes
# per run on reserveCache retries. In host-mode the real
# caches live in $HOME (~/go/pkg/mod, ~/.cache/go-build) and
# persist between jobs without any actions/cache plumbing.
cache: false
- name: Run Go tests - name: Run Go tests
# client/ is the deprecated Fyne client; excluded from CI per # client/ is the deprecated Fyne client; excluded from CI per
+1 -2
View File
@@ -53,8 +53,7 @@ jobs:
uses: actions/setup-go@v5 uses: actions/setup-go@v5
with: with:
go-version-file: go.work go-version-file: go.work
# See go-unit.yaml for why `cache: true` is disabled. cache: true
cache: false
- name: Run integration suite - name: Run integration suite
# `make integration` precleans leftover docker-compose state and # `make integration` precleans leftover docker-compose state and
+3 -3
View File
@@ -37,8 +37,7 @@ jobs:
uses: actions/setup-go@v5 uses: actions/setup-go@v5
with: with:
go-version-file: go.work go-version-file: go.work
# See go-unit.yaml for why `cache: true` is disabled. cache: true
cache: false
- name: Set up pnpm - name: Set up pnpm
uses: pnpm/action-setup@v4 uses: pnpm/action-setup@v4
@@ -49,7 +48,8 @@ jobs:
uses: actions/setup-node@v4 uses: actions/setup-node@v4
with: with:
node-version: 22 node-version: 22
# See dev-deploy.yaml for why `cache: pnpm` is disabled. cache: pnpm
cache-dependency-path: ui/pnpm-lock.yaml
- name: Resolve image tag - name: Resolve image tag
id: tag id: tag
+2 -5
View File
@@ -37,11 +37,8 @@ jobs:
uses: actions/setup-node@v4 uses: actions/setup-node@v4
with: with:
node-version: 22 node-version: 22
# `cache: pnpm` pushes the pnpm store through the Gitea cache: pnpm
# Actions cache service which is currently unreachable cache-dependency-path: ui/pnpm-lock.yaml
# (192.168.0.222:43513 ETIMEDOUT). In host-mode the real
# store lives in ~/.local/share/pnpm and persists between
# jobs without any action plumbing.
- name: Install npm dependencies - name: Install npm dependencies
working-directory: ui working-directory: ui