Rename deploy runner label to cube-host
CI / check (push) Successful in 6m26s
CI / deploy (push) Successful in 22s

This commit is contained in:
randy committed 2026-08-28 20:38:16 +02:00
1 parent 3fbd97a0bd
commit 60170efda2
2 files changed
+5 -5

No files matched your search

+3 -3
View File
@@ -10,7 +10,7 @@ instance:
`ubuntu-latest`/`ubuntu-24.04`/`ubuntu-22.04` — runs the `check` job
in a fresh, isolated container per job, same as before.
* A dedicated native runner, installed directly on the host (no Docker
around it), label `deploy:host` — runs only the `deploy` job.
around it), label `cube-host` — runs only the `deploy` job.
They're separate because the Docker-based runner's jobs (whether in
its usual isolated per-job containers, or tried directly inside its
@@ -50,7 +50,7 @@ label:
----
runner:
labels:
- "deploy:host"
- "cube-host"
----
The `host` scheme means jobs run directly via the runner process's own
@@ -110,7 +110,7 @@ usernames, e.g. `randy,friend1,friend2` — not their emails, the
== CI deploy job
`.gitea/workflows/ci.yml`'s `deploy` job runs after `check` passes, only
on a push to `main`, with `runs-on: deploy`:
on a push to `main`, with `runs-on: cube-host`:
. Checks out the repo with plain `git` (`fetch` + `checkout`,
authenticated via a one-off `http.extraHeader`) rather than