All checks were successful
CI / skip-ci-check (pull_request) Successful in 6s
CI / ansible-validation (pull_request) Successful in 46s
CI / lint-and-test (pull_request) Successful in 51s
CI / secret-scanning (pull_request) Successful in 6s
CI / dependency-scan (pull_request) Successful in 15s
CI / license-check (pull_request) Successful in 13s
CI / sast-scan (pull_request) Successful in 24s
CI / vault-check (pull_request) Successful in 11s
CI / container-scan (pull_request) Successful in 6s
CI / sonar-analysis (pull_request) Successful in 5s
CI / playbook-test (pull_request) Successful in 25s
CI / workflow-summary (pull_request) Successful in 4s
Inventory and Caddy playbook for levkin LXC 220; Makefile target caddy-levkin. Document git-ci-01 disk (64G), capacity 2, prune cron, and pve201 RAM limits in host_vars and homelab guides. Co-authored-by: Cursor <cursoragent@cursor.com>
19 lines
797 B
YAML
19 lines
797 B
YAML
---
|
||
# git-ci-01 — Gitea Actions runner (VM 115 on pve201 @ 10.0.10.223)
|
||
ansible_become_exe: /usr/bin/sudo
|
||
ansible_become_method: sudo
|
||
|
||
# Proxmox (manual / qm): VMID 115, 2 cores, 4096 MB RAM, 64 GB disk (scsi0)
|
||
# act_runner: /etc/act_runner/config.yaml — capacity 2, force_pull false
|
||
# Maintenance: /etc/cron.weekly/docker-prune-ci (docker system prune -af --filter until=168h)
|
||
#
|
||
# Capacity notes (2026-05-23):
|
||
# - pve201: ~3 GB RAM free (125 Gi total, heavily overcommitted — GPU VM 104 @ 72 Gi)
|
||
# - capacity 3 needs ~8–12 GB RAM on this VM → migrate runner to pve10 or add RAM after freeing pve201
|
||
# - 12 repos: capacity 2 on one runner is OK; second runner on pve10 if queues stack up
|
||
|
||
git_ci_runner_capacity: 2
|
||
git_ci_disk_gb: 64
|
||
git_ci_proxmox_vmid: 115
|
||
git_ci_proxmox_node: pve201
|