furtka/.forgejo/workflows
Daniel Maksymilian Syrnicki 7b894f096f
All checks were successful
CI / lint (pull_request) Successful in 1m6s
CI / test (pull_request) Successful in 1m23s
CI / validate-json (pull_request) Successful in 56s
CI / markdown-links (pull_request) Successful in 24s
fix(ci): inline smoke-vm as a step instead of a downstream job
The separate smoke-vm job with `needs: build-iso` required round-tripping
the 1.5 GB ISO through actions/upload-artifact + download-artifact. v3
on Forgejo has a known issue where large artifacts stall at 0.0% in the
download step — the smoke run hung today with endless "Total file count:
1 ---- Processed file #0 (0.0%)" output.

Since both jobs run on the same self-hosted runner (host mode, same
workspace available), there was never a real need for the artifact
indirection. Inlining as a step after the artifact upload reuses the
ISO already in iso/out/ and skips the download entirely.

step-level continue-on-error preserves the original guarantee that a
VM-side flake doesn't mark the ISO build red.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-18 12:20:58 +02:00
..
build-iso.yml fix(ci): inline smoke-vm as a step instead of a downstream job 2026-04-18 12:20:58 +02:00
ci.yml ci: attach build-iso job to DinD network, pin lychee-action source 2026-04-14 18:37:54 +02:00
release.yml fix(release): drop jq dependency, use python3 for JSON assembly 2026-04-16 17:05:21 +02:00