I1: Decide the shared runner usage policy #43

Open
opened 2026-11-09 17:05:59 +00:00 by claude · 1 comment
Member

Decide which owners and repos may use the shared runner, and whether Actions is on by default for new repos. Options and a recommendation are in the private assessment (Nextcloud: eom.dev Plans/CI-CD Readiness Assessment.md).

Work (Claude): comment with the exact configuration each option needs.
Decision (Eric): pick one.

Acceptance: the decision is recorded here and implementation issues are updated to match.

Decide which owners and repos may use the shared runner, and whether Actions is on by default for new repos. Options and a recommendation are in the private assessment (Nextcloud: `eom.dev Plans/CI-CD Readiness Assessment.md`). **Work (Claude)**: comment with the exact configuration each option needs. **Decision (Eric)**: pick one. **Acceptance**: the decision is recorded here and implementation issues are updated to match.
claude added this to the CI/CD 1: Runner policy and isolation milestone 2026-11-09 17:05:59 +00:00
claude added the needs-eric
priority
high
cicd
labels 2026-11-09 17:05:59 +00:00
claude added this to the CI/CD Roadmap project 2026-11-09 17:07:33 +00:00
Author
Member

Options with the configuration each needs. Recommendation: option 1.

Where things stand: 89 of 91 public repos have the Actions unit on, because it's on by default. Workflows exist only under DevOps, Gaming and claude. Setting names below were checked against Gitea 1.27.0's app.example.ini.

1. Allowlist by runner scope (recommended)
The runner is registered to the DevOps org, the Gaming org and the claude user, not to the whole instance. Other owners' repos have no runner.

  • Role: a new list, gitea_actions_runner_scopes: [DevOps, Gaming, claude]. For each entry the role creates a registration token with gitea actions generate-runner-token --scope <owner>, keeps it in its own Secret, and starts one runner registered with it. A runner process holds one registration, so three scopes means three runner processes. I'd confirm that with runner 2.0.1 when writing it.
  • Role: gitea.config.repository.DEFAULT_REPO_UNITS: repo.code,repo.releases,repo.issues,repo.pulls,repo.wiki,repo.projects,repo.packages. That's the default list without repo.actions, so new repos start with Actions off. An owner on the allowlist turns it on in the repo's settings.
  • Eric, once: after the scoped runners show as online, delete the instance-level runner under Site Administration → Actions → Runners.
  • Existing repos of other owners keep their Actions tab. A workflow there would wait for a runner and be cancelled after 12 hours by the timeout from S6 (#39).
  • Adding an owner later is one line in the list and a rerun of --tags actions.
  • Cost: three runner processes share one Docker daemon, so up to three jobs can run at once. I'd cap CPU and memory per job container to keep that within the host. On a VM (see #45) this is three small services. In the cluster it's three Helm releases, each with its own Docker, which is heavier.

2. Off by default, runner stays instance-wide

  • Role: only the DEFAULT_REPO_UNITS line above.
  • This changes the starting point, not who may use the runner: any repo owner can still turn Actions on.
  • Smallest change. Applying it restarts Gitea, since it's an app.ini change.

3. Open to everyone, as today

  • No configuration change. Fair use rests on the one-job queue and timeouts from S4 and S6, and on the outcome of #44 and #45.

Not an option: DISABLED_REPO_UNITS = repo.actions turns Actions off for every repo, including DevOps.

Questions for the decision

  • Is the allowlist DevOps, Gaming and claude, or should your other orgs and personal repos be on it too? None of them has a workflow today.
  • Options 1 and 2 need ansible-playbook gitea.yaml without --tags actions for the app.ini line, which restarts Gitea for a minute or so.

The reasoning behind the recommendation is in the private assessment. Once you pick, I'll update #44, #48 and #72 to match and write the role change.

— eom-cicd-roadmap

**Options with the configuration each needs. Recommendation: option 1.** Where things stand: 89 of 91 public repos have the Actions unit on, because it's on by default. Workflows exist only under DevOps, Gaming and `claude`. Setting names below were checked against Gitea 1.27.0's `app.example.ini`. **1. Allowlist by runner scope (recommended)** The runner is registered to the DevOps org, the Gaming org and the `claude` user, not to the whole instance. Other owners' repos have no runner. - Role: a new list, `gitea_actions_runner_scopes: [DevOps, Gaming, claude]`. For each entry the role creates a registration token with `gitea actions generate-runner-token --scope <owner>`, keeps it in its own Secret, and starts one runner registered with it. A runner process holds one registration, so three scopes means three runner processes. I'd confirm that with runner 2.0.1 when writing it. - Role: `gitea.config.repository.DEFAULT_REPO_UNITS: repo.code,repo.releases,repo.issues,repo.pulls,repo.wiki,repo.projects,repo.packages`. That's the default list without `repo.actions`, so new repos start with Actions off. An owner on the allowlist turns it on in the repo's settings. - Eric, once: after the scoped runners show as online, delete the instance-level runner under Site Administration → Actions → Runners. - Existing repos of other owners keep their Actions tab. A workflow there would wait for a runner and be cancelled after 12 hours by the timeout from S6 (#39). - Adding an owner later is one line in the list and a rerun of `--tags actions`. - Cost: three runner processes share one Docker daemon, so up to three jobs can run at once. I'd cap CPU and memory per job container to keep that within the host. On a VM (see #45) this is three small services. In the cluster it's three Helm releases, each with its own Docker, which is heavier. **2. Off by default, runner stays instance-wide** - Role: only the `DEFAULT_REPO_UNITS` line above. - This changes the starting point, not who may use the runner: any repo owner can still turn Actions on. - Smallest change. Applying it restarts Gitea, since it's an `app.ini` change. **3. Open to everyone, as today** - No configuration change. Fair use rests on the one-job queue and timeouts from S4 and S6, and on the outcome of #44 and #45. Not an option: `DISABLED_REPO_UNITS = repo.actions` turns Actions off for every repo, including DevOps. **Questions for the decision** - Is the allowlist DevOps, Gaming and `claude`, or should your other orgs and personal repos be on it too? None of them has a workflow today. - Options 1 and 2 need `ansible-playbook gitea.yaml` without `--tags actions` for the `app.ini` line, which restarts Gitea for a minute or so. The reasoning behind the recommendation is in the private assessment. Once you pick, I'll update #44, #48 and #72 to match and write the role change. — eom-cicd-roadmap
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DevOps/software-infrastructure#43