Use shared S3 compilation cache and unsigned Harbor SBOMs #39
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/shared-s3-cache-unsigned-sbom"
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?
Releases no longer require Cosign keys or public Rekor/Sigstore. Syft SPDX inventories are published as unsigned Harbor OCI referrers; subject digest, manifest/blob integrity and downloaded bytes are verified before promotion of the identical candidate image digest.
Local Cargo/setup, CI, BuildKit and native C/C++ compilation use the same mandatory Ceph S3 cache. Private credential files and BuildKit file secrets preserve existing keys. A private filtered lifecycle/error ledger survives normal SDK daemon restarts, including S3 read failures treated as misses. Backend failures prevent success; final-daemon hit counts are labeled accurately.
Own test wall-clock watchdogs, shortened fixture shutdown budgets and kill timers have been removed. Tests observe real processing, errors, state changes and complete joins/reaps. Actual specification and library defaults remain; application timeout contracts use controlled virtual time where appropriate.
Validation: the complete local just gate returned exit 0, including 59 cache behavior cases and all required Rust, data and browser checks. Real Rust/C cache miss→hit and SDK restart/cleanup canaries passed. Already user-merged main updates are integrated. Exact protected CI and the unsigned Harbor release round-trip are still required.