Add two Forgejo runners on dev-new as microVMs with their own label #465

New issue

Closed

opened 2026-10-13 01:32:13 +02:00 by dominik.polakovics · 0 comments

dominik.polakovics commented

2026-10-13 01:32:13 +02:00

Owner

Constraints: dev-new is wifi-only (no bridged taps) and holds the coding-lab, onecli, warpgate and diag secrets, so CI must stay behind a VM boundary and must not see /run/secrets.

fw's two runners (fj-runner-1/2) are single-vCPU microVMs on a saturated N100 at the lowest CPU weight. dev-new has 16 threads and 26 GiB free. Add two runner microVMs there, keep the fw runners, and register the new ones only with a `dev-new` label so workflows opt in with `runs-on: dev-new`. Constraints: dev-new is wifi-only (no bridged taps) and holds the coding-lab, onecli, warpgate and diag secrets, so CI must stay behind a VM boundary and must not see `/run/secrets`.

dominik.polakovics referenced this issue from a pull request that will close it,

2026-10-13 01:32:55 +02:00

feat(dev-new): two Forgejo runner microVMs behind the dev-new label #466

dominik.polakovics closed this issue

2026-10-13 01:38:06 +02:00