runner: cron lane (green-tea-runner-cron) and og-badges on it
New Fly app green-tea-runner-cron (shared-cpu-1x, 2GB, label cron, same config.yaml: 30s fetch timeout, 1h job cap) takes scheduled/ops jobs so deploys on green-tea-runner never wait behind them. og-badges now runs-on: cron. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VVFi3wvLWKaEkpDw6eLnQC
This commit is contained in:
1 parent
a21a12db05
commit
15a3cc9bd0
2 files changed
+31
-1
No files matched your search
@@ -16,7 +16,7 @@ on:
|
||||
default: 'false'
|
||||
jobs:
|
||||
badges:
|
||||
runs-on: ubuntu-latest
|
||||
runs-on: cron
|
||||
timeout-minutes: 8
|
||||
steps:
|
||||
- name: define, diff, award
|
||||
|
||||
@@ -0,0 +1,30 @@
|
||||
# Fly app green-tea-runner-cron: cron-lane Gitea Actions runner (label `cron`) for scheduled/ops jobs, so they never queue ahead of deploys.
|
||||
# Deploy: cd runner && fly deploy -c fly.cron.toml. Registration token is a Fly secret.
|
||||
app = "green-tea-runner-cron"
|
||||
primary_region = "iad"
|
||||
|
||||
[build]
|
||||
image = "docker.gitea.com/act_runner:5.0.0-dind"
|
||||
|
||||
[experimental]
|
||||
# Fly's rootfs is overlay, so Docker's data root must live on the volume.
|
||||
entrypoint = ["sh", "-c", "mkdir -p /data/docker && rm -rf /var/lib/docker && ln -sfn /data/docker /var/lib/docker && exec s6-svscan /etc/s6"]
|
||||
|
||||
[env]
|
||||
DOCKER_HOST = "unix:///var/run/docker.sock"
|
||||
GITEA_INSTANCE_URL = "https://teahub.xyz"
|
||||
GITEA_RUNNER_LABELS = "cron:docker://node:22-bookworm"
|
||||
GITEA_RUNNER_NAME = "fly-iad-cron-1"
|
||||
CONFIG_FILE = "/etc/gitea-runner/config.yaml"
|
||||
|
||||
[[files]]
|
||||
guest_path = "/etc/gitea-runner/config.yaml"
|
||||
local_path = "config.yaml"
|
||||
|
||||
[mounts]
|
||||
source = "runner_cron_data"
|
||||
destination = "/data"
|
||||
|
||||
[[vm]]
|
||||
size = "shared-cpu-1x"
|
||||
memory = "2gb"
|
||||
Reference in new issue
Block a user