Menu

Why rust-cache doesn't make your Rust CI fast (tauri: 246 s to 53 s)
📰

Why rust-cache doesn't make your Rust CI fast (tauri: 246 s to 53 s)

DEV Community: rust·Tom·about 22 hours ago
#VSLnNt3F
#devtorust#devto#dev#cache#crates
Reading 0:00
15s threshold

Swatinem/rust-cache, the cache step in most Rust CI, saves your dependencies and deliberately leaves out your workspace crates. It also sets CARGO_INCREMENTAL=0 . On GitHub's runners every job starts on a new VM, so every warm job, full cache hit and all, compiles your own crates again. No rust-cache setting makes that go away. What does is a target/ still there from the last job: Cargo then skips every crate that hasn't changed.

Skipbox keeps it for you. Your job runs on your account's own machine, which keeps the checkout and Cargo's target/ between jobs.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.