From a1e65a4d47388a6f730c51699ce56e0049cf8e48 Mon Sep 17 00:00:00 2001 From: agw Date: Wed, 30 Sep 2026 19:30:00 +0200 Subject: [PATCH] Mount the host work directory into the build job docker run -v ${WORK_DIR}:/work reaches the runner host's docker daemon, so it mounts the host's /srv/jasp-build, not the job container's. The job prepared its scripts in a private copy that never reached the build, which has been running a stale build-jasp.sh left on the host since 2 September (22 modules, no remotes pre-seed) and failing every night on "The package remotes is required". The publish steps had the same blind spot for out/. Claude-Session: https://claude.ai/code/session_01GGe7kUhooMFuzY6GaDb2w9 --- .gitea/workflows/build.yml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.gitea/workflows/build.yml b/.gitea/workflows/build.yml index c311805..82db269 100644 --- a/.gitea/workflows/build.yml +++ b/.gitea/workflows/build.yml @@ -55,6 +55,15 @@ jobs: # full build runs for hours. The act_runner timeout and Gitea's # ENDLESS_TASK_TIMEOUT must both allow for this (see README). timeout-minutes: 900 + # `docker run -v ${WORK_DIR}:/work` below talks to the runner host's docker, + # so it mounts the *host's* WORK_DIR. Without this bind the job container + # has its own private copy: the scripts it prepares never reach the build + # (which then ran a stale script left on the host) and the tarball the + # build writes is invisible to the publish steps. + container: + image: docker.gitea.com/runner-images:ubuntu-latest + volumes: + - /srv/jasp-build:/srv/jasp-build steps: - uses: actions/checkout@v4