Files

fix: wait for the build again now the runner reaper reads the job log

v1.0.5 cut the wait budget to 720s because gongfoo's output-stall reaper
sampled the runner container's log, which never carries step output — any step
over ~15 minutes was killed however much it printed, and successful builds were
reported as failures.

gongfoo#4 is fixed and deployed: the reaper now derives progress from the Gitea
job log, which does see our heartbeat. So the short budget is now the wrong
trade — it returns success while the build is still running, which is how
monsoon run 66 reported green on a build that had another ten minutes to go.

Raise the budget to 2700s. That is comfortably above a ~25 minute Rust release
build and under gongfoo's default 3600s absolute wall-clock cap, so we always
return a verdict of our own rather than being reaped mid-wait.

The heartbeat is now load-bearing rather than diagnostic: it is the signal
keeping a long job alive. Noted in CLAUDE.md so it does not get tidied away.

2026-08-07 16:37:08 +03:00

3.2 KiB

Raw Blame History

copr-publish

Gitea composite action that submits a source RPM to Fedora COPR, watches the build, and dumps each chroot's builder-live.log into the CI output as collapsible groups.

Why use this

copr-cli build by itself only prints status transitions (pending / importing / running / succeeded). When a build fails you have to click through to the COPR web UI to see the actual log. This action:

Submits with --nowait and captures the build ID.
Prints a clickable https://copr.fedorainfracloud.org/coprs/build/... link so you can follow live.
Streams status transitions from copr-cli watch-build while polling COPR for the build's actual state, so the job's verdict comes from the build rather than from the health of a long-lived connection.
On completion, fetches each chroot's builder-live.log via copr-cli download-build and emits them as ::group:: blocks.
Fails CI if the build fails. A build merely still running when the wait budget expires is reported, not failed.
Returns within COPR_WAIT_BUDGET whatever happens, so the step finishes before a CI runner's step limit kills it.

Environment overrides

Variable	Default	Purpose
`COPR_WAIT_BUDGET`	`2700`	Seconds to wait for the build before returning. A build still running at expiry is reported as such and the step exits 0 — CI runners commonly kill a step long before a large build finishes.
`COPR_POLL_INTERVAL`	`30`	Seconds between build-state polls.

Requirements

The runner must already have:

copr-cli on PATH (provided by the copr-cli RPM on Fedora runners).
grep -P (PCRE, default on Fedora).

Inputs

Input	Required	Description
`project`	yes	COPR project in the form `<owner>/<project>`, e.g. `helexa/cortex`.
`srpm`	yes	Path or glob to the source RPM(s) to submit, e.g. `*.src.rpm`.
`copr-config`	yes	Contents of `~/.config/copr`. Fetch from https://copr.fedorainfracloud.org/api/ and store as a repo or org secret.

Usage

jobs:
  publish:
    runs-on: fedora
    steps:
      - uses: actions/download-artifact@v3
        with:
          name: my-srpm

      - name: Publish to COPR
        uses: https://git.lair.cafe/actions/copr-publish@v1
        with:
          project: helexa/cortex
          srpm: '*.src.rpm'
          copr-config: ${{ secrets.COPR_CONFIG }}

Note the fully-qualified URL in uses: — the Gitea instance's DEFAULT_ACTIONS_URL points at github.com, so internal actions must be referenced by absolute URL.

Versioning

Pin to a major version tag (@v1) for automatic patch/minor updates. Pin to an exact tag (@v1.0.3) to freeze.

Obtaining `COPR_CONFIG`

Log in to https://copr.fedorainfracloud.org/.
Visit https://copr.fedorainfracloud.org/api/.
Copy the entire [copr-cli] config block.
Save as a Gitea secret named COPR_CONFIG in the consuming repo (or at org level to share across all org repos).

3.2 KiB Raw Blame History