11 Commits

Author SHA1 Message Date
Gan, Jimmy 10e48461d4 fix(ci): use Gitea container IP for checkout in claude-dev workflow
Deploy Claude Dev (Dev) / deploy-claude-dev-dev (push) Failing after 16m58s
Replaces 'gitea:3000' with '172.21.0.4:3000' to bypass DNS
resolution issues in act job containers. Also removed --dns
override from runner-config.yaml which was breaking Docker's
embedded DNS and container name resolution.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 11:52:34 +08:00
Gan, Jimmy d29c2c3a13 Validate cached venv by testing pytest, not just python binary
The cached venv's python binary may work but tool symlinks (pytest, etc.)
break when restored in a different environment. Test pytest specifically
to catch this.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 11:50:31 +08:00
Gan, Jimmy 951d68f022 Validate cached venv before use (test python binary works)
Deploy Dashboard (Main) / Frontend Tests (push) Has been cancelled
Deploy Dashboard (Main) / Deploy to Production (push) Has been cancelled
Deploy Dashboard (Main) / Backend Tests (push) Has been cancelled
Cached venvs from NAS Docker containers have broken symlinks when
restored on the VPS host, causing "pytest: command not found".
Add a functional check that venv/bin/python runs before accepting
the cache as valid.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 11:42:24 +08:00
Gan, Jimmy c8b87561a8 feat(claude-dev): mount full /volume1 and NAS root into container
Deploy Claude Dev (Dev) / deploy-claude-dev-dev (push) Failing after 12m12s
Added bind mounts:
- /volume1:/volume1 — full Synology data volume
- /:/nas-root — host root filesystem (system config, crontab, etc.)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 11:25:14 +08:00
Gan, Jimmy 6fce702820 fix(claude-dev): add env_file to docker-compose for ANTHROPIC env vars
Deploy Claude Dev (Dev) / deploy-claude-dev-dev (push) Has been cancelled
Deploy Dashboard (Dev) / Backend Tests (push) Failing after 11m13s
Deploy Dashboard (Dev) / Frontend Tests (push) Failing after 15m4s
Deploy Dashboard (Dev) / Deploy to Dev (push) Has been skipped
The NAS deployment already had this line; syncing back to source
so future CI deploys don't wipe it.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 11:16:57 +08:00
Gan, Jimmy 6ed875ae81 Move test jobs to VPS runner, keep deploy on NAS
Backend and frontend tests now run on `runs-on: vps` (server2 at
158.101.140.85, host mode) with checkout via Tailscale IP. Deploy
job stays on `runs-on: nas` with gitea_gitea network for Docker
socket access. This eliminates the HDD bottleneck and Docker
network/DNS issues that plagued the all-NAS pipeline.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 11:09:38 +08:00
Gan, Jimmy aa19085538 Add container network: gitea_gitea to backend/frontend test jobs
Job containers were created on isolated bridge networks that couldn't
reach Gitea at any address. Add workflow-level container blocks to
backend-tests and frontend-tests (matching deploy job) so all job
containers are on the gitea network and can resolve "gitea" via
Docker's embedded DNS. Revert checkout URLs back to gitea:3000.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 03:59:54 +08:00
Gan, Jimmy fa2d96d58a Use NAS LAN IP for checkout (192.168.31.221:3300)
host.docker.internal doesn't resolve in job containers despite the
runner config setting --add-host. Use the NAS LAN IP directly,
which is reachable from any Docker bridge network.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 03:56:21 +08:00
Gan, Jimmy 9e72e8abdf Use host.docker.internal:3300 for checkout instead of gitea:3000
Job containers are on their own bridge networks and can't reach
172.21.0.4 (Gitea's IP on gitea_gitea network). Use the Docker host
gateway with port 3300 (which maps to Gitea container's 3000) instead.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 03:53:25 +08:00
Gan, Jimmy ab24bd8526 Add gitea hosts entry before checkout steps to work around DNS override
Runner's --dns options bypass Docker's embedded DNS resolver, so job
containers can't resolve the "gitea" hostname even when connected to the
gitea_gitea network. Add /etc/hosts entry pointing gitea to 172.21.0.4
before each checkout step.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-03 03:34:43 +08:00
Gan, Jimmy fccdf64435 Increase pip install timeout from 300s to 600s for cold-cache HDD slowness
Cold venv installs on the NAS HDD exceed 300s, causing the backend
tests install step to be killed by timeout. Double the timeout so the
first or fallback pip mirror attempt can complete before the timeout
fires.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-06-03 01:34:00 +08:00
3 changed files with 21 additions and 17 deletions
+1 -1
View File
@@ -22,7 +22,7 @@ jobs:
- name: Checkout repository
run: |
if [ ! -d .git ]; then
git clone --branch "${GITHUB_REF_NAME}" --depth=1 "http://gitea:3000/${GITHUB_REPOSITORY}.git" .
git clone --branch "${GITHUB_REF_NAME}" --depth=1 "http://172.21.0.4:3000/${GITHUB_REPOSITORY}.git" .
fi
- name: Resolve image tags
+16 -16
View File
@@ -14,7 +14,7 @@ concurrency:
jobs:
backend-tests:
name: Backend Tests
runs-on: ubuntu-latest
runs-on: vps
env:
SECRET_KEY: test-secret-key-for-ci-environment-32chars-minimum
@@ -22,7 +22,7 @@ jobs:
- name: Checkout repository
run: |
if [ ! -d .git ]; then
git clone --depth=1 "http://gitea:3000/${GITHUB_REPOSITORY}.git" .
git clone --depth=1 "http://100.78.131.124:3300/${GITHUB_REPOSITORY}.git" .
fi
- name: Setup Python
@@ -55,32 +55,32 @@ jobs:
cd dashboard/backend
if [ "${{ steps.cache-python.outputs.cache-hit }}" = "true" ]; then
echo "Restoring venv from cache $CACHE_KEY..."
if cp -a $CACHE_DIR/venv . && [ -f venv/bin/activate ]; then
if cp -a $CACHE_DIR/venv . && [ -f venv/bin/activate ] && venv/bin/python -m pytest --version >/dev/null 2>&1; then
echo "Cache restored successfully"
else
echo "Cache corrupted, installing fresh..."
rm -rf venv
python3 -m venv venv
. venv/bin/activate
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR --retries 3 --timeout 30 -r requirements.txt || \
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR --index-url https://pypi.tuna.tsinghua.edu.cn/simple --trusted-host pypi.tuna.tsinghua.edu.cn -r requirements.txt || \
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR --retries 3 --timeout 30 -r requirements.txt || \
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR --index-url https://pypi.tuna.tsinghua.edu.cn/simple --trusted-host pypi.tuna.tsinghua.edu.cn -r requirements.txt || \
pip install -r requirements.txt
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR --retries 3 --timeout 30 -r requirements-dev.txt || \
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR --index-url https://pypi.tuna.tsinghua.edu.cn/simple --trusted-host pypi.tuna.tsinghua.edu.cn -r requirements-dev.txt || \
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR --retries 3 --timeout 30 -r requirements-dev.txt || \
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR --index-url https://pypi.tuna.tsinghua.edu.cn/simple --trusted-host pypi.tuna.tsinghua.edu.cn -r requirements-dev.txt || \
pip install -r requirements-dev.txt
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR pytest-timeout pytest-cov || pip install pytest-timeout pytest-cov
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR pytest-timeout pytest-cov || pip install pytest-timeout pytest-cov
fi
else
echo "Installing fresh dependencies..."
python3 -m venv venv
. venv/bin/activate
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR --retries 3 --timeout 30 -r requirements.txt || \
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR --index-url https://pypi.tuna.tsinghua.edu.cn/simple --trusted-host pypi.tuna.tsinghua.edu.cn -r requirements.txt || \
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR --retries 3 --timeout 30 -r requirements.txt || \
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR --index-url https://pypi.tuna.tsinghua.edu.cn/simple --trusted-host pypi.tuna.tsinghua.edu.cn -r requirements.txt || \
pip install -r requirements.txt
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR --retries 3 --timeout 30 -r requirements-dev.txt || \
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR --index-url https://pypi.tuna.tsinghua.edu.cn/simple --trusted-host pypi.tuna.tsinghua.edu.cn -r requirements-dev.txt || \
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR --retries 3 --timeout 30 -r requirements-dev.txt || \
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR --index-url https://pypi.tuna.tsinghua.edu.cn/simple --trusted-host pypi.tuna.tsinghua.edu.cn -r requirements-dev.txt || \
pip install -r requirements-dev.txt
timeout 300 pip install --cache-dir=$PIP_CACHE_DIR pytest-timeout pytest-cov || pip install pytest-timeout pytest-cov
timeout 600 pip install --cache-dir=$PIP_CACHE_DIR pytest-timeout pytest-cov || pip install pytest-timeout pytest-cov
echo "Saving venv to cache $CACHE_KEY..."
cp -a venv $CACHE_DIR/ || echo "Warning: cache save failed"
fi
@@ -102,13 +102,13 @@ jobs:
frontend-tests:
name: Frontend Tests
runs-on: ubuntu-latest
runs-on: vps
steps:
- name: Checkout repository
run: |
if [ ! -d .git ]; then
git clone --depth=1 "http://gitea:3000/${GITHUB_REPOSITORY}.git" .
git clone --depth=1 "http://100.78.131.124:3300/${GITHUB_REPOSITORY}.git" .
fi
- name: Setup Node.js
@@ -170,7 +170,7 @@ jobs:
deploy:
name: Deploy to Production
runs-on: ubuntu-latest
runs-on: nas
if: always()
needs: [backend-tests, frontend-tests]
env:
+4
View File
@@ -7,9 +7,13 @@ services:
stdin_open: true
tty: true
working_dir: /repos/nas-tools
env_file:
- /volume1/docker/claude-dev/.env
volumes:
- /volume1/repos:/repos
- /volume1/docker/claude-dev/claude-config:/root/.claude
- /volume1/docker/claude-dev/claude-config/.claude.json:/root/.claude.json
- /volume1/docker/claude-dev/gitea_token:/root/.gitea_token:ro
- /volume1/docker/claude-dev/bashrc:/root/.bashrc
- /volume1:/volume1
- /:/nas-root