marcel/familienarchiv
1
0
Fork 0
Code Issues 118 Pull Requests 2 Actions 4 Packages Projects Releases Wiki Activity

fix(workflows): match runner label — runs-on ubuntu-latest (#508) #509

Merged
marcel merged 1 commits from fix/issue-508-runner-label-self-hosted-to-ubuntu into main 2026-05-11 16:18:40 +02:00
Conversation 0 Commits 1 Files Changed 2 +10 -2
marcel commented 2026-05-11 16:16:32 +02:00
Owner
Copy Link

Summary

Closes #508.

Both .gitea/workflows/nightly.yml and release.yml had runs-on: self-hosted, but our gitea-runner advertises ubuntu-latest / ubuntu-24.04 / ubuntu-22.04 — no runner has self-hosted. Dispatched deploy jobs parked in the queue indefinitely (run 1483, run 1492, …).

Fix

Change runs-on: self-hosted → runs-on: ubuntu-latest in both files. The runner is still self-hosted in the architectural sense (DooD socket, joined to gitea_gitea net, single-tenant per ADR-011). The "self-hosted" string was just a label-name assumption that didn't match reality.

Added an inline comment in nightly.yml explaining the choice and confirming it stays within ADR-011's single-tenant promise (which is a repo-level boundary, not a label-level one).

Test plan

  • runs-on value matches a label the runner actually advertises
  • After merge: re-dispatch nightly.yml. Job picks up. Staging stack builds and up -d --wait succeeds.

🤖 Generated with Claude Code

## Summary Closes #508. Both `.gitea/workflows/nightly.yml` and `release.yml` had `runs-on: self-hosted`, but our `gitea-runner` advertises `ubuntu-latest / ubuntu-24.04 / ubuntu-22.04` — no runner has `self-hosted`. Dispatched deploy jobs parked in the queue indefinitely (run 1483, run 1492, …). ## Fix Change `runs-on: self-hosted` → `runs-on: ubuntu-latest` in both files. The runner is still self-hosted in the architectural sense (DooD socket, joined to `gitea_gitea` net, single-tenant per ADR-011). The "self-hosted" string was just a label-name assumption that didn't match reality. Added an inline comment in nightly.yml explaining the choice and confirming it stays within ADR-011's single-tenant promise (which is a repo-level boundary, not a label-level one). ## Test plan - [x] `runs-on` value matches a label the runner actually advertises - [ ] After merge: re-dispatch `nightly.yml`. Job picks up. Staging stack builds and `up -d --wait` succeeds. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
marcel added 1 commit 2026-05-11 16:16:32 +02:00
fix(workflows): match runner label — runs-on ubuntu-latest, not self-hosted
Some checks failed
CI / Unit & Component Tests (pull_request) Has been cancelled
Details
CI / OCR Service Tests (pull_request) Has been cancelled
Details
CI / Backend Unit Tests (pull_request) Has been cancelled
Details
CI / fail2ban Regex (pull_request) Has been cancelled
Details
CI / Compose Bucket Idempotency (pull_request) Has been cancelled
Details
CI / Unit & Component Tests (push) Failing after 2m49s
Details
CI / Backend Unit Tests (push) Has been cancelled
Details
CI / fail2ban Regex (push) Has been cancelled
Details
CI / Compose Bucket Idempotency (push) Has been cancelled
Details
CI / OCR Service Tests (push) Has been cancelled
Details
54a8f7f8e9 
Closes #508.

Our gitea-runner advertises labels ubuntu-latest / ubuntu-24.04 /
ubuntu-22.04. `runs-on: self-hosted` never matches → dispatched
deploy jobs sit in the queue forever. The runner is still
genuinely self-hosted (DooD socket, joined to gitea_gitea net,
single-tenant per ADR-011) — the `self-hosted` token was just an
unconfirmed assumption about the label name.

Unblocks #497 / #499 first deploy.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
marcel merged commit 54a8f7f8e9 into main 2026-05-11 16:18:40 +02:00
marcel deleted branch fix/issue-508-runner-label-self-hosted-to-ubuntu 2026-05-11 16:18:41 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
P0-critical
Blocks a core user journey, causes data loss, or is a security/accessibility barrier. Work on this before P1+.
 P1-high
Significant friction on a main user journey; workaround exists but is non-obvious. Next up after P0.
 P2-medium
Noticeable improvement; doesn't block anything; schedule opportunistically.
 P3-later
Cosmetic or parking-lot work; fine to stay open indefinitely.
 audit
Read-only audit / assessment work; produces a report rather than changing code
 bug
Something isn't working
 cleanup
Removal of dead code, vague comments, naming violations, and scratch artifacts
 collaboration
We want to extend the family archive to have more collaboration tools
 conversation
descoped
We will do that later
 devops
documentation
README, ARCHITECTURE, GLOSSARY, CONTRIBUTING, per-domain docs
 epic
Marker for epic-level issues that group multiple child issues
 feature
file-upload
legibility
Codebase Legibility Refactor — preparing the codebase for human evaluation and bus-factor reduction
 notification
person
phase-1: security
Security hygiene — must be done first
 phase-2: container-images
Production-ready multi-stage Docker images
 phase-3: prod-compose
Production compose overlay + Caddy reverse proxy
 phase-4: spring-prod-profile
Spring Boot production configuration profile
 phase-5: backups
Database and object storage backup strategy
 phase-6: deployment-docs
.env.example, DEPLOYMENT.md, runbook
 phase-7: monitoring
Prometheus, Loki, Grafana, Alertmanager
 refactor
Code restructuring without behaviour change
 security
test
ui
UI/UX and accessibility issues
 user
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Jens marcel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marcel/familienarchiv#509
Delete Branch "fix/issue-508-runner-label-self-hosted-to-ubuntu"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?