CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
ci/woodpecker/push/woodpecker Pipeline was successful
Add tools/ci/release_evidence.py (marqdo.release-gates.v1) plus unit tests: missing/skipped/FAIL/UNVERIFIED and tested_sha mismatches stay DO_NOT_RELEASE, performance may be PASS/WARN, unknown gate names are rejected. The GitHub CI now has a release-evidence job that maps the Linux/schema and native matrix results onto the manifest and uploads it, and both CI systems run the evidence-tool tests. Clear the contradictions the RFC calls out: remove the stale CURRENT.md rows that claimed DNS/TLS/UDP and fs metadata were absent while the same table said they were implemented; correct docs/ci.md to state that the GitHub-hosted Windows/macOS matrix exists (Woodpecker has no such agent); keep the old convergence plan historical; require the evidence manifest in releasing.md; and add a docs-consistency guard for these claims. This is step 6 of the CI/security RFC (B05/B06/B07).
1.5 KiB
1.5 KiB
CI evidence tools
strict-evidence.py
Writes marqdo.strict-evidence.v1, called by tests/security/run-lane.sh when
MARQDO_STRICT_EVIDENCE is set and by the self-hosted security workflow. It
records only measured or explicitly supplied facts:
tested_shaand whether it came fromgit rev-parseor an operator env;- source archive SHA256 (and whether it matched the expected digest);
- kernel/uname/cgroup2/container,
uid/root, bwrap/rustc/cargo/cc versions; - runner kind, image digest, run URL, start/finish and outcome.
A root-only PASS is rejected. PASS from a container or a persistent
self-hosted runner with production credentials is not valid G-C evidence; see
docs/security-vm.md.
release_evidence.py
Aggregates per-gate results into marqdo.release-gates.v1:
python3 tools/ci/release_evidence.py \
--target-sha "$SHA" \
--gate "linux=PASS:$SHA:https://ci.example/run/1" \
--gate "windows=PASS:$SHA:https://ci.example/run/2" \
--gate "macos=PASS:$SHA:https://ci.example/run/3" \
--gate "strict_vm=PASS:$SHA:https://ci.example/run/4" \
--gate "performance=WARN:$SHA:https://ci.example/run/5" \
--out "docs/evidence/ci/$SHA/manifest.json"
A missing gate becomes UNVERIFIED. Any non-PASS required gate, a
tested_sha different from target_sha, an unknown gate name or a malformed
SHA forces DO_NOT_RELEASE. performance may be PASS or WARN.
Unit tests: python3 -m unittest discover -s tools/ci -p 'test_*.py'.