xavierk/Fenris
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases 11 Wiki Activity

Task: Check Gitea Actions runner availability on git.bongbetic.com #37

New Issue
Closed
opened 2026-09-02 18:31:21 +00:00 by xavierk · 1 comment
xavierk commented 2026-09-02 18:31:21 +00:00
Owner
Copy Link
Copy Source

Parent map: Fenris deb + rpm release plan

Question

Determine whether Gitea Actions is usable on git.bongbetic.com for tag-driven package builds: repo-level has_actions, any registered runner (try admin runners endpoint — the tea login is an instance admin), runner labels/arch. Verdict: CI = Gitea Actions on tag push, or manual build fallback. If no runner, name the cheapest enablement option.

Parent map: [Fenris deb + rpm release plan](https://git.bongbetic.com/xavierk/Fenris/issues/33) ## Question Determine whether Gitea Actions is usable on git.bongbetic.com for tag-driven package builds: repo-level `has_actions`, any registered runner (try admin runners endpoint — the tea login is an instance admin), runner labels/arch. Verdict: CI = Gitea Actions on tag push, or manual build fallback. If no runner, name the cheapest enablement option.
xavierk added this to the Wayfinder: Fenris deb + rpm release plan milestone 2026-09-02 18:31:21 +00:00
xavierk added the wayfinder:task label 2026-09-02 18:31:21 +00:00
xavierk self-assigned this 2026-09-02 18:43:08 +00:00
xavierk commented 2026-09-02 18:43:30 +00:00
Author
Owner
Copy Link
Copy Source

Verdict: manual build fallback — no runner registered

Gitea Actions is enabled but idle: repo-level Actions is on, yet zero runners are registered instance-wide, so any tag-driven workflow would queue forever.

Evidence (read-only, 2026-09-03)

Check Result
GET /api/v1/repos/xavierk/Fenris has_actions: true, not archived
GET /api/v1/admin/actions/runners (instance admin) {"runners": [], "total_count": 0}

The admin runners endpoint answering 200 (not 404) also confirms the Actions feature is enabled at instance level — only the runner fleet is missing.

Consequence for the #33 release plan

  • Tag push → workflow would stay waiting for a runner indefinitely. CI = manual build for now: build deb + rpm locally, publish via authenticated PUT to the Gitea Debian/RPM registries (as planned in #33, independent of Actions).
  • A workflow file (.gitea/workflows/release.yml) can still be committed now — it stays dormant until a runner exists, and makes later enablement zero-touch.

Cheapest enablement option

Single act_runner (static Go binary) on the existing host that already runs Gitea:

  1. Instance admin generates runner registration token (Site Administration → Actions → Runners, or POST /api/v1/admin/actions/runners/registration-token).
  2. act_runner register --instance https://git.bongbetic.com --token <reg-token> --labels ubuntu-latest:host:// (host mode: no Docker needed; sufficient for dpkg-buildpackage/rpmbuild + upload).
  3. act_runner daemon under a systemd unit.

No new machine, no container runtime required in host-label mode — one binary plus a unit file.

## Verdict: **manual build fallback** — no runner registered Gitea Actions is **enabled but idle**: repo-level Actions is on, yet zero runners are registered instance-wide, so any tag-driven workflow would queue forever. ### Evidence (read-only, 2026-09-03) | Check | Result | |---|---| | `GET /api/v1/repos/xavierk/Fenris` | `has_actions: true`, not archived | | `GET /api/v1/admin/actions/runners` (instance admin) | `{"runners": [], "total_count": 0}` | The admin runners endpoint answering 200 (not 404) also confirms the Actions feature is enabled at instance level — only the runner fleet is missing. ### Consequence for the #33 release plan - Tag push → workflow would stay `waiting for a runner` indefinitely. **CI = manual build** for now: build deb + rpm locally, publish via authenticated PUT to the Gitea Debian/RPM registries (as planned in #33, independent of Actions). - A workflow file (`.gitea/workflows/release.yml`) can still be committed now — it stays dormant until a runner exists, and makes later enablement zero-touch. ### Cheapest enablement option Single **`act_runner`** (static Go binary) on the existing host that already runs Gitea: 1. Instance admin generates runner registration token (Site Administration → Actions → Runners, or `POST /api/v1/admin/actions/runners/registration-token`). 2. `act_runner register --instance https://git.bongbetic.com --token <reg-token> --labels ubuntu-latest:host://` (host mode: no Docker needed; sufficient for `dpkg-buildpackage`/`rpmbuild` + upload). 3. `act_runner daemon` under a systemd unit. No new machine, no container runtime required in host-label mode — one binary plus a unit file. - closes #37
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ready-for-agent
Spec triaged and ready for an implementing agent
 wayfinder:grilling
HITL conversational decision ticket
 wayfinder:map
Canonical Wayfinder decision map
 wayfinder:prototype
HITL prototype decision ticket
 wayfinder:research
AFK research decision ticket
 wayfinder:task
Prerequisite task ticket
No labels wayfinder:task
Milestone
No items
No Milestone Wayfinder: Fenris deb + rpm release plan
Projects
Clear projects
No projects
Assignees
Clear assignees
xavierk (Xavier Karma)
No Assignees xavierk
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: xavierk/Fenris#37