fix(ci): keep verification in job logs and make coverage explicit #325
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/lean-ci-and-persistent-cache"
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?
CI and release retain the full behavior suite while removing report uploads/downloads, screenshots and separate diagnostics. Regular tests no longer use coverage instrumentation; explicit development coverage prints results from a separate build directory. Runtime image acceptance, legacy import, restore and rollback comparisons remain unchanged and use owned temporary data. The unsigned digest-bound SBOM stays in Harbor.
Shared S3 and Docker layer caches remain active; owned compiler daemons use SCCACHE_IDLE_TIMEOUT=0 and explicit cleanup.
Validation: both thematic changes passed local just gate; 15 runtime fixture behavior tests passed. Local native tool tests used the existing Bun 1.3.14; Forgejo validates pinned Bun 1.4.2 and the production image acceptance.
The native Erlang/OTP CI toolchain bootstrap also runs inside the shared cache wrapper with its own credential scope; C/C++ compilation is cached, while package downloads and BEAM compilation retain their normal paths. Full local just gate passed after this correction.