littlefox/neokom
Watch
1
2
Fork
You've already forked neokom
 1
Code Issues 9 Pull requests 1 Projects Releases 12 Packages Activity Actions

CI: keep each job's output as a logs artifact #159

Merged
littlefox merged 2 commits from ci-logs-artifacts into main 2026-10-19 12:08:14 +00:00
Conversation 0 Commits 2 Files changed 4 +133 -2
littlefox commented 2026-10-19 11:06:26 +00:00
Owner
Copy link

CI job logs readable from here: every run step's output is tee'd to ci-logs/.log by a workflow default shell, uploaded as logs- (always, failed or not), and fetched with tools/forge.py logs RUN [--job J]. ci.yml and packaging.yml. Forgejo 15 has no log API, and its web log endpoint returns no steps to a token.

Verified: the shell template locally (a failing step still fails with its exit code and stops at the first error, and both steps are logged); this PR's own CI run, read with forge.py logs.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8

CI job logs readable from here: every run step's output is tee'd to ci-logs/<job>.log by a workflow default shell, uploaded as logs-<job> (always, failed or not), and fetched with `tools/forge.py logs RUN [--job J]`. ci.yml and packaging.yml. Forgejo 15 has no log API, and its web log endpoint returns no steps to a token. Verified: the shell template locally (a failing step still fails with its exit code and stops at the first error, and both steps are logged); this PR's own CI run, read with forge.py logs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
CI: keep each job's output as a logs artifact, read with forge.py logs
Some checks failed
packaging / fedora (pull_request) Has started running
Details
packaging / nix (pull_request) Has started running
Details
packaging / arch (pull_request) Successful in 13m38s
Details
ci / check (push) Successful in 13m55s
Details
ci / desktop (push) Successful in 18m55s
Details
ci / e2e (push) Successful in 26m9s
Details
packaging / debian (pull_request) Successful in 26m13s
Details
packaging / release (pull_request) Has been cancelled
Details
5e8bf6495a 
Forgejo has no API for job logs, and the web page only gives them to a
logged-in browser, so a failed job couldn't be diagnosed from here (the
desktop failure on #158). Every run step's output is now also written
to ci-logs/<job>.log by a default shell and uploaded as logs-<job>,
which a token can fetch. CLAUDE.md gets the command, and the three
clippy runs CI does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
forge.py logs: download by the run's id, list by its number
All checks were successful
packaging / arch (pull_request) Successful in 10m39s
Details
packaging / debian (pull_request) Successful in 25m26s
Details
ci / check (push) Successful in 13m34s
Details
packaging / nix (pull_request) Successful in 25m52s
Details
ci / e2e (push) Successful in 29m10s
Details
packaging / fedora (pull_request) Successful in 33m33s
Details
ci / desktop (push) Successful in 18m29s
Details
packaging / release (pull_request) Has been skipped
Details
d714cb69d4 
The artifact list takes the run number shown everywhere, but the
download takes Forgejo's internal run id; with the number it fetched
another run's artifact or none.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
littlefox referenced this pull request from a commit 2026-10-19 21:34:01 +00:00
Release 0.4.0
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
area/ci
Forgejo Actions, runner, tests

  
area/desktop
Desktop build

  
area/packaging
Arch, Debian, Fedora, NixOS packages

  
area/protocol
kom-proto, wire format, charset

  
area/reading
Unread tracking, reading order, review

  
area/ui
Dioxus app, layout, interaction

  
area/web
Web build and relay

  
area/writing
Composing and sending texts

  
kind/bug
Something is broken

  
kind/feature
New functionality

  
kind/infra
Tooling, tests, CI, dev environment

  
kind/request
requests for features or changes from users

  
needs/user
Waiting for a decision or action from littlefox

  
parked
Kept for reference; no work planned until the user says so

  
perf
Run the perf workflow and its budgets on this pull request (#287)

  
security
Security-relevant

  
upstream
A proposal for Protocol A or lyskomd, for the LysKOM development group

No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
littlefox/neokom!159
No description provided.