Explain server image publish gate

This commit is contained in:
dingo
2026-10-11 08:26:53 -04:00
parent c3f25a621e
commit 93ed872f3f
2 changed files with 14 additions and 0 deletions
+3
View File
@@ -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]
+11
View File
@@ -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.