From 745874c7a0f3b38966cf70092e338f6d7ae9b47a Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 12 Jul 2026 00:57:35 +0200 Subject: [PATCH] docs(wp-0014): close vergabe Forgejo deploy (dfbc13a) Image pushed to forgejo.coulomb.social and deployed on CoulombCore; health smoke passed. Retires Gitea image for vergabe-teilnahme. --- ...WP-0014-core-hub-helm-cutover-vergabe-refresh.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/workplans/RAILIANCE-WP-0014-core-hub-helm-cutover-vergabe-refresh.md b/workplans/RAILIANCE-WP-0014-core-hub-helm-cutover-vergabe-refresh.md index 4f87e4d..7ebedc8 100644 --- a/workplans/RAILIANCE-WP-0014-core-hub-helm-cutover-vergabe-refresh.md +++ b/workplans/RAILIANCE-WP-0014-core-hub-helm-cutover-vergabe-refresh.md @@ -66,7 +66,7 @@ Post-deploy `make core-hub-status` and `make core-hub-smoke` passed on ```task id: RAILIANCE-WP-0014-T04 -status: progress +status: done priority: medium state_hub_task_id: "d547f68d-52ec-4ff1-952b-ec70c834e0d3" ``` @@ -83,16 +83,17 @@ in `vergabe-teilnahme` Dockerfile (`dfbc13a`); workflow aligned with `issue-core` gained `publish-forgejo` + `.forgejo/workflows/publish-python-package.yml` so PyPI can move off Gitea (`uv.lock` still pins Gitea wheel URLs until publish). -**Remaining:** push `forgejo.coulomb.social/coulomb/vergabe-teilnahme:dfbc13a` -(CI on railiance01 or `docker login` + `docker push`), then -`VERGABE_IMAGE_TAG=dfbc13a make vergabe-deploy`. Live cluster still -`gitea...:f95de14`. +**Deployed 2026-07-12:** operator `docker login forgejo.coulomb.social`; image +`forgejo.coulomb.social/coulomb/vergabe-teilnahme:dfbc13a` pushed manually; +`VERGABE_IMAGE_TAG=dfbc13a make vergabe-deploy` (Helm rev 3). Pod healthy; +`https://vergabe-teilnahme.whywhynot.de/health/` → 200. Gitea image retired +for this workload. ## Post-deploy vergabe smoke and runbook evidence ```task id: RAILIANCE-WP-0014-T05 -status: wait +status: done priority: medium state_hub_task_id: "4eaaa345-4252-46c1-bd8a-49d654ec48f4" ```