Files
marqdo-cli/docs/ci.md
T
cflmy 0d7e11b6f1
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
ci: aggregate SHA-bound release evidence and clear status drift
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).
2026-11-21 17:29:48 +08:00

2.9 KiB

CI/CD

Current setup

  • Git remote: https://git.cflmy.cn/cflmy/marqdo-cli.git
  • Woodpecker: https://ci.cflmy.cn
  • Pipeline definition: .woodpecker.yml
  • Credentials are local-only and ignored; see development-credentials.md. Do not put tokens in pipeline files or commit messages.

The default Docker pipeline runs on push and pull request:

test:
  rustup component add clippy rustfmt
  apt install curl/ca-certificates/python3 + Node.js 22
  cargo fmt --all -- --check
  cargo clippy --workspace --all-targets -- -D warnings
  cargo test --workspace --locked
  python3 -m unittest discover -s tools/ci -p "test_*.py"

build (depends on test):
  cargo build --release --locked -p marqdo-cli

Node.js 22 is required because the optional foreign-kernel tests use ES-module syntax; Debian bookworm's Node 18 fails those tests.

Language contract note. cargo test --workspace includes conformance fixtures that execute .mq.md source under RFC-LANG-0002. The implementation, stdlib digest and corpus are green at ffd1cc9; a red executable-source suite is a real regression, not an expected migration state. Do not "fix" it by restoring the old mapper or regenerating goldens; see STATUS.md. The pipeline definition itself (fmt/clippy/test/build, security lane, platform gaps) is unchanged.

What this pipeline does not cover

  • Strict security lane: needs a disposable VM/self-hosted runner with Bubblewrap/AppArmor namespace support. See security-vm.md and security-gate.md. The Docker pipeline is not an OS-isolation proof.
  • Windows/macOS native lanes: the GitHub-hosted .github/workflows/ci.yml matrix does exist and does run on windows-latest and macos-latest. The Woodpecker instance itself has no Windows/macOS agent, so a Woodpecker-only green pipeline cannot substitute for those native jobs. A remote Windows/macOS PASS requires the GitHub matrix (or an equivalent real native runner) on the same SHA.
  • Performance baseline (G4): needs a fixed Linux node; see performance.md. Development-container or TCG/QEMU timings are SMOKE, never release evidence.
  • Release publication/signing: no publication job is defined. The release-evidence job produces a SHA-bound manifest artifact; it does not tag or upload a release.

Local reproduction

export PATH="$HOME/.cargo/bin:$PATH"
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace --locked
cargo build --release --locked -p marqdo-cli

Local API/trigger

The ignored .secrets/dev.env may contain a Woodpecker API token for local queries/triggers. The token is not needed by the pipeline itself and must never be committed.