e949e2d794
Some checks are pending
Veza CI / Backend (Go) (push) Waiting to run
Veza CI / Frontend (Web) (push) Waiting to run
Veza CI / Rust (Stream Server) (push) Waiting to run
Veza CI / Notify on failure (push) Blocked by required conditions
Security Scan / Secret Scanning (gitleaks) (push) Waiting to run
Before this commit, every push touching veza-stream-server triggered three parallel Rust workflows that did essentially the same work: - ci.yml Rust job : build + test + clippy + fmt + audit - rust-ci.yml : clippy + test + tarpaulin coverage - stream-ci.yml : clippy + audit + test With the runner at capacity=4, this meant 3 of the 4 parallel slots burned on duplicate Rust compilation while Backend/Frontend waited. Each Rust build is ~3-5 min warm, so the redundancy was costing ~10 min per Rust-touching push. Consolidate into a single job in ci.yml: - Adds the tarpaulin coverage step + 50% threshold gate from rust-ci - Adds the upload-artifact step for the coverage JSON - Deletes rust-ci.yml and stream-ci.yml All Rust CI now happens in ci.yml's `rust` job. The Cargo cache, rustup cache and tool-binary cache already set up in the prior commit keep everything warm. |
||
|---|---|---|
| .. | ||
| accessibility.yml.disabled | ||
| backend-ci.yml | ||
| cd.yml.disabled | ||
| chromatic.yml.disabled | ||
| ci.yml | ||
| commitlint.yml.disabled | ||
| container-scan.yml.disabled | ||
| contract-testing.yml.disabled | ||
| flaky-report.yml.disabled | ||
| frontend-ci.yml | ||
| go-fuzz.yml | ||
| load-test-nightly.yml.disabled | ||
| mutation-testing.yml.disabled | ||
| openapi-lint.yml.disabled | ||
| performance.yml.disabled | ||
| rust-mutation.yml.disabled | ||
| sast.yml.disabled | ||
| security-scan.yml | ||
| semgrep.yml.disabled | ||
| staging-validation.yml.disabled | ||
| storybook-audit.yml.disabled | ||
| trivy-fs.yml | ||
| visual-regression.yml.disabled | ||
| zap-dast.yml.disabled | ||