Commit graph

2 commits

Author SHA1 Message Date
trvon
09dd84492f
ci: run the runner probe twice a day
The Security Hub probe on ghost-ci reads the newest successful runner-probe.yml run and
alerts after 26 h; the workflow had no schedule, so it never ran on its own.
2026-11-21 09:44:37 -07:00
trvon
f58a765033
CI: Forgejo release workflow, test lane and runner probe
All checks were successful
release / draft (push) Has been skipped
release / build (debian:trixie, trixie) (push) Successful in 31m13s
release / build (ubuntu:24.04, noble) (push) Successful in 26m59s
release / publish (push) Has been skipped
release.yml builds, tests and packs a Linux install tree per distro
(debian:trixie, ubuntu:24.04), one at a time with JOBS=2 and nice.
Branches (main, ci/**) and PRs run the test lane and print each sha256;
a v* tag uploads the tarballs and .sha256 files to a draft release and
publishes it only when every build passed.

runner-probe.yml checks that a runner with the docker label picks up
jobs, can clone this repo with the job token and reach the API.

packaging/ci/build-release.sh is the shared build step. It refuses to
run outside CI because it installs packages.

Forgejo now reads .forgejo/workflows and ignores .github/workflows,
whose ubuntu-24.04/macos-15 labels no runner here provides.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 18:26:02 -07:00