eabf207e3f
All checks were successful
release / build-and-release (push) Successful in 43s
On any ERROR step, xetup now files an issue in the private x9/xetup-runs tracker (title "FAILED <host> - <version> - <date>", label "failed", body = step table + tail-capped Deploy.log) via the xetup-bot write:issue token, baked in through -ldflags. Best-effort and non-blocking; successful runs stay silent and the email is the fallback. The deployment email now attaches the zipped Deploy.log and links to this run's issue plus the run history filtered to this machine. - internal/buildinfo: ldflags-injected Version + RunsToken - internal/runreport: issue filing, retries, tail-capped log - internal/report: multipart/mixed with zip attachment, tracker links; buildMessage split out and covered by report_test.go - release.yml: inject Version (tag/SHA) + FORGEJO_RUNS_TOKEN via ldflags Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
13 lines
489 B
Go
13 lines
489 B
Go
// Package buildinfo holds values injected at build time via -ldflags -X.
|
|
// Defaults keep local (non-CI) builds working: no token means run reporting
|
|
// is silently skipped, and version shows "dev".
|
|
package buildinfo
|
|
|
|
var (
|
|
// Version is the git tag (e.g. "v0.10") or short commit SHA of this build.
|
|
Version = "dev"
|
|
|
|
// RunsToken is the Forgejo write:issue token for the x9/xetup-runs repo.
|
|
// Empty on local builds -> runreport is a no-op (see internal/runreport).
|
|
RunsToken = ""
|
|
)
|