ci: rc-publish workflow on main; make test gets CI's 30m timeout #1184
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci-rc-publish"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This adds
.forgejo/workflows/rc-publish.ymlto 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.workflow_dispatch). Pushes and tags never start it.ref: a commit SHA or a branch name;version: a pre-release only (vX.Y.Z-<suffix>; a plainvX.Y.Zis refused, so it can never take a real release's tag);image:yesorno(a string; an API dispatch turned the earlier boolean into false).cairnd-linux-amd64with its sha256 and buildinfo, uploaded to the generic packagecairnd/<version>. Withimage: yes, it also pushes the multi-arch image under the same tag, using ko exactly as release.yml does.It also changes
make testtogo 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, somake testpanicked locally.One more commit only updates two comments: the image input is
yes/no, and the W5 playbook (homelab-config PR #65) is gone.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