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
ci/woodpecker/push/woodpecker Pipeline was successful
- Add docs/ci.md with the pipeline, Node 22 requirement, local credential policy and explicit non-coverage (strict VM, Windows/macOS, release publish). - Update README/STATUS: private remote and Woodpecker CI are available; G-C strict and native lanes remain separate. - Keep ADR-0039 stdlib-in-repo intent and its docs references. Gate: fmt, clippy -D warnings, 440 tests passed.
1.6 KiB
1.6 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 + Node.js 22
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace --locked
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.
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. The Docker pipeline is not an OS-isolation proof.
- Windows/macOS native lanes: no runners are configured.
- Release publication/signing: no release job is defined.
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.