From 93ed872f3f1ad9a09e80f456419771843f4d0bbb Mon Sep 17 00:00:00 2001 From: dingo Date: Sun, 11 Oct 2026 08:26:53 -0400 Subject: [PATCH] Explain server image publish gate --- .gitea/workflows/build.yaml | 3 +++ docs/engineering/VALIDATION.md | 11 +++++++++++ 2 files changed, 14 insertions(+) diff --git a/.gitea/workflows/build.yaml b/.gitea/workflows/build.yaml index fe09ca7..1920fa6 100644 --- a/.gitea/workflows/build.yaml +++ b/.gitea/workflows/build.yaml @@ -142,6 +142,9 @@ jobs: exit 0 fi bash tools/ci/publish-image.sh + - name: Explain disabled server-image publishing + if: ${{ gitea.ref == 'refs/heads/main' && gitea.event_name != 'pull_request' && vars.HARBOR_SERVER_REPOSITORY == '' }} + run: echo 'Server image was not pushed to Harbor: set the HARBOR_SERVER_REPOSITORY Gitea variable.' image: needs: [checks] diff --git a/docs/engineering/VALIDATION.md b/docs/engineering/VALIDATION.md index c926b14..d522ff4 100644 --- a/docs/engineering/VALIDATION.md +++ b/docs/engineering/VALIDATION.md @@ -6856,3 +6856,14 @@ The maintainer reports there have been no successful server image builds since connectivity does not establish that the current cellular client/server pair works. Resume the probe once a deployable server image is available. CI image-job success is not deployment evidence and does not satisfy this gate. + +## 2026-10-11 — Server image pipeline diagnosis + +The latest relevant M11 code run (#272) failed in the checks matrix, so its +dependent `server-image` job was canceled. The next code run (#273) was canceled +by a subsequent push before its dependent image jobs started. Runs #274–#278 +were green but their changes were documentation-only; `ci-paths.sh` therefore +skipped the server-image build. This explains why those green runs produced no +new image. Harbor publication has a separate gate: the main-branch job pushes +only when `HARBOR_SERVER_REPOSITORY` is configured. That repository variable is +not visible from this workspace, so its current value is unverified.