Trigger the homelab GitOps deploy tick manually and read its result from the journal.
npx skills add https://github.com/DanielH2018/server --skill gitops-tick-danielh2018
Please help me install this Agent Skill. Skill: gitops-tick Source: https://github.com/DanielH2018/server/tree/main/.claude/skills/gitops-tick Command: npx skills add https://github.com/DanielH2018/server --skill gitops-tick-danielh2018
gitops_tick.sh on daniel-box to start gitops-deploy.service immediately via a polkit-authorized wrapper, executing the real fetch, CI-gate, fast-forward merge, deploy, health-gate, and rollback path. - Result interpretation: Prints last_run, hold_sha, and behind_since from /var/lib/gitops-deploy so a fresh last_run distinguishes an uneventful tick from a tick that never ran. - Concurrency and exit-code handling: Detects when a tick is joined to an already-running one, and surfaces exit code 75 (still running) or 3 (skipped for lock contention). - Use Case: After merging an urgent fix, run the tick by hand instead of waiting ten minutes, then confirm from last_run that the deploy actually executed. ## Quick Start Ask the agent to run ./scripts/deploy_tools/gitops_tick.sh on daniel-box and report the tick's journal output and last_run timestamp.High-intent search queries and answers about installing and using this skill.
Run ./scripts/deploy_tools/gitops_tick.sh on daniel-box to start gitops-deploy.service immediately. It executes the identical code path as the timer: fetch, CI gate, fast-forward merge, deploy, health gate, and rollback.
The deployer only logs on deferrals, alerts, or real deploys, so a healthy uneventful tick prints nothing. Check the last_run timestamp in /var/lib/gitops-deploy to distinguish "ticked, nothing to do" from "did not tick".
Yes, but the tick is joined rather than duplicated. Systemd coalesces the request into the run already activating, and the wrapper detects this and reports it instead of starting a second deploy.
It is a system unit, so unprivileged starts are refused with "Interactive authentication required". A polkit rule grants the deploy user only the start verb on this unit, which is why the wrapper script exists.
Exit 75 means the tick was still running when the script stopped watching. Exit 3 means the tick was skipped due to lock contention, so nothing deployed and nothing alerted.
No. The wrapper runs the identical code path as the timer, performing a real fetch, merge, deploy, health gate, and rollback. There is no rehearsal mode.
trevorbyrumCommit and push staged code changes to a GitHub repository branch.
LucasSantana-DevInspect pods, manage Helm releases, and debug k3s clusters.
tranhieuttAutomate secure CI/CD pipelines with GitOps and progressive delivery.
lloydchangAutomate GitOps deployments and lifecycle management for Kubernetes environments.