ci: rc-publish workflow on main; make test gets CI's 30m timeout #1184

Merged
Cordy merged 7 commits from ci-rc-publish into main 2026-11-18 21:02:43 +00:00
Owner

This adds .forgejo/workflows/rc-publish.yml to main, so release candidates no longer have to be dispatched from a drifting branch. It was used for the #742 W5 runs: rc1 to rc5, fake1, and k8s1 to k8s3.

  • Manual only (workflow_dispatch). Pushes and tags never start it.
  • Inputs:
    • ref: a commit SHA or a branch name;
    • version: a pre-release only (vX.Y.Z-<suffix>; a plain vX.Y.Z is refused, so it can never take a real release's tag);
    • image: yes or no (a string; an API dispatch turned the earlier boolean into false).
  • Output: cairnd-linux-amd64 with its sha256 and buildinfo, uploaded to the generic package cairnd/<version>. With image: yes, it also pushes the multi-arch image under the same tag, using ko exactly as release.yml does.
  • Same hardening as release.yml: reap strays, emptied workspace, fresh GOCACHE, go mod download + verify.

It also changes make test to go test -timeout 30m ./..., matching CI. cmd/cairnd alone runs 10 to 14 minutes since v0.6.409, longer than go test's 10-minute default, so make test panicked locally.

One more commit only updates two comments: the image input is yes/no, and the W5 playbook (homelab-config PR #65) is gone.

This adds `.forgejo/workflows/rc-publish.yml` to main, so release candidates no longer have to be dispatched from a drifting branch. It was used for the #742 W5 runs: rc1 to rc5, fake1, and k8s1 to k8s3. - **Manual only** (`workflow_dispatch`). Pushes and tags never start it. - **Inputs:** - `ref`: a commit SHA or a branch name; - `version`: a pre-release only (`vX.Y.Z-<suffix>`; a plain `vX.Y.Z` is refused, so it can never take a real release's tag); - `image`: `yes` or `no` (a string; an API dispatch turned the earlier boolean into false). - **Output:** `cairnd-linux-amd64` with its sha256 and buildinfo, uploaded to the generic package `cairnd/<version>`. With `image: yes`, it also pushes the multi-arch image under the same tag, using ko exactly as release.yml does. - **Same hardening as release.yml:** reap strays, emptied workspace, fresh GOCACHE, go mod download + verify. It also changes `make test` to `go test -timeout 30m ./...`, matching CI. cmd/cairnd alone runs 10 to 14 minutes since v0.6.409, longer than go test's 10-minute default, so `make test` panicked locally. One more commit only updates two comments: the image input is `yes`/`no`, and the W5 playbook (homelab-config PR #65) is gone.
make test: -timeout 30m like CI (cmd/cairnd runs past go test's 10-minute default)
Some checks failed
ci / test-and-build (pull_request) Failing after 3m29s
5b99819693
Cordy changed title from ci: rc-publish workflow on main (manual pre-release builds of any commit) to ci: rc-publish workflow on main; make test gets CI's 30m timeout 2026-11-18 19:37:02 +00:00
Merge remote-tracking branch 'origin/main' into ci-rc-publish-main
All checks were successful
ci / test-and-build (pull_request) Successful in 19m30s
da21eaec2b
Cordy merged commit 76298c497d into main 2026-11-18 21:02:43 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1184
No description provided.