Eliminate CI Disk Pressure by Using Ripr Binary Directly

说明与用途

CI 现在使用预构建的 Ripr 二进制文件，消除了编译 xtask 的需求，降低了磁盘压力。

问题

CI runs compile the repo’s xtask orchestration layer on every run, creating a 5‑8 GB build tree that causes disk‑full failures on self‑hosted runners.

结果

CI runs now use the prebuilt Ripr binary, removing the 5‑8 GB build tree, eliminating disk‑full failures, and reducing latency.

工作流

• Audit each cargo xtask ripr-* step in .github/workflows/ripr.yml and map it to an equivalent ripr <subcommand> call.
• Replace cargo xtask ripr-* steps with direct ripr <subcommand> commands in the workflow.
• For orchestration logic not covered by Ripr, either add a new Ripr subcommand or build a slim standalone gate binary once and cache it.
• Configure the workflow to use a pinned Ripr release asset or the setup-ripr action instead of cargo install ripr.
• Verify that the job produces the same evidence artifacts (target/ripr/** and target/receipts/**).
• Confirm that the CI no longer compiles the workspace and that disk pressure is eliminated.

证据

The recurring CX43 self-hosted-runner disk pressure is a downstream integration-shape problem in this repo, not a ripr deficiency.

来源

The ripr binary is fully capable and already does the static analysis — our xtask/src/tasks/ripr_evidence.rs shells out to it.

来源