Strict Rust & Cargo
Warm target/ + sccache[self-hosted, Linux, X64]

Self-Hosted Rust & Cargo GitHub Actions Runners

Short answer: Rust CI lives and dies by incremental compilation and Cargo registry warmth. Strict keeps Cargo caches on fast local NVMe while cleaning up safely in Tiers 2–3 when disks tighten, plus Tailnet cache sharing across machines.

Eliminate cold Cargo builds and 10 GB cache eviction with warm NVMe target directories and 7-tier disk safety.

Drop-in workflow YAML & zero-sudo enrollment

Enroll your host with strict add-runner and route jobs directly via GitHub's native runs-on labels:

.github/workflows/ci.yml
jobs:
  cargo:
    runs-on: [self-hosted, Linux, X64]
    steps:
      - uses: actions/checkout@v4
      - run: cargo test --locked
Enroll runner host
curl -fsSL https://strict.ai/install.sh | sh
strict add-runner owner/rust-service --labels self-hosted,Linux,X64,rust

How Strict keeps Rust & Cargo runners healthy

SubsystemHow it applies to Rust & Cargo
Disk CleanupTier 2 trims stale Cargo/npm/Bun package caches and Tier 3 sweeps git-ignored build leftovers only when disk dips below lowGiB—preserving active incremental state whenever space allows.
Preflight Doctordisk-headroom tracks tight Rust target/ growth; dns-github checks crates.io/GitHub reachability.
Tracked Toolchainsrust, docker, go, node, bun, runner
Cache & BalancingCPU load-skew load balancing prevents two concurrent cargo test --release runs from saturating one box while a sibling server sits idle.

When Strict fits vs. when hosted runners win

Use Strict for Rust & Cargo when

  • Full bare-metal multi-core throughput for parallel rustc codegen units
  • No 10 GB remote Actions Cache ceiling evicting target/ dependencies
  • Consistent rustc toolchain monitoring across every Linux and macOS host

Use cloud-hosted runners when

  • Public Rust crates accepting arbitrary untrusted PRs
  • Windows-specific MSVC build matrix targets

Frequently asked questions

How does Strict handle huge Rust target/ directories?

estimate_reclaimable() measures runner and package caches every 300s, and Tiers 2–3 progressively reclaim old artifacts when free disk falls below lowGiB without deleting active workspaces.

Does Strict monitor Rust compiler drift across runners?

Yes. collect_toolchains() records rust versions on every 30-second heartbeat and highlights mismatches within the same OS pool.

Can Rust builds run on both macOS Apple Silicon and Linux hosts?

Yes. Label macOS hosts for universal Apple binary builds and Linux X64/ARM64 servers for server binaries under one fleet.

Try Strict on one spare Mac in under two minutes

Signed Apple Silicon app or single-line CLI · Zero accounts required