coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(wp-0014): record Forgejo CI fix and deploy blocker
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 4s
Details

Browse source
This commit is contained in:
tegwick 2026-07-12 00:45:56 +02:00
parent 115d7a4095
commit 859d0051b3
1 changed files with 14 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

18
workplans/RAILIANCE-WP-0014-core-hub-helm-cutover-vergabe-refresh.md
View file

@ -73,10 +73,20 @@ state_hub_task_id: "d547f68d-52ec-4ff1-952b-ec70c834e0d3"
2026-07-11: Migrated deploy target to **Forgejo OCI** (`forgejo.coulomb.social`).
Added `.forgejo/workflows/image.yaml` in `vergabe-teilnahme`; Makefile
`check-vergabe-image` gates deploy. `helm/vergabe-teilnahme-values.yaml` uses
Forgejo repository + tag `1061f3e`. Image must be published to Forgejo (CI push
to `main` or `docker login forgejo.coulomb.social && docker push`). Gitea registry
is retired for this app. Live cluster still at `gitea...:f95de14` until deploy.
`check-vergabe-image` gates deploy. `helm/vergabe-teilnahme-values.yaml` targets
Forgejo repository + tag `dfbc13a`.
2026-07-12: **CI root cause fixed** — Forgejo Actions run failed because
`uv sync` resolved `issue-core` from Forgejo PyPI (404). Fix: `uv sync --frozen`
in `vergabe-teilnahme` Dockerfile (`dfbc13a`); workflow aligned with
`railiance-enablement` container-build template. Local docker build verified.
`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`.
## Post-deploy vergabe smoke and runbook evidence