• First party
  • cargo test cargos integrated testing tool
  • cargo check cargos integrated checking tool
  • cargo build cargos integrated build tool
  • cargo bench Used by cargos benching feature or crates like citerion
• Additional RustUp components
  • cargo miri test for testing using miri -> rustup component miri is needed
• Cargo plugins
  • cargo udeps to analyze for unused dependencies -> cargo plugin cargo-udeps is needed
  • cargo tarpaulin generate code coverage reports -> cargo plugin cargo-tarpaulin is needed
  • cargo nextest the next generation test runner for cargo -> cargo plugin cargo-nextest is needed

for more information run cargo all-features --help

If certain projects, features might add up and CI jobs can take longer. In order to shrink wall time of your builds you can specify --chunks (the total amount of junks to split into [1..]) and --chunk (the chunk nr of the one executed command [1..<CHUNKS>]) per execution.

I.e. in github you can use a job matrix:

name: CI

on: [pull_request]

jobs:
  build:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        chunk: [1,2,3,4]
        chunks: 4
    steps:
    - uses: actions/checkout@v2
    - name: Install stable toolchain
        uses: actions-rs/toolchain@v1
        with:
          profile: minimal
          toolchain: stable
          override: true
     - name: Install cargo-all-features
        uses: actions-rs/cargo@v1
        with:
          command: install
          args: cargo-all-features --version 1.8.0
    - name: Build all features for release
      run: cargo all-features build --chunks  ${{matrix.chunks}} --chunk  ${{matrix.chunk}} -- --release

You are not sure if you configured something correct but don't have the time to wait for all tests or builds? Use --dry-run, it will skip all command execution.

If you are not sure if the correct command are executed use --verbose

Don't mind to use +<toolchain> or any other combination of rustups toolchain selection. cargo-all-features will pick up on the active toolchain and use it.

for more information run cargo all-features --help

If you never heard of cross, an almost zero setup cross compilation cli setup

While there is no way to directly know if you are calling this cargo subcommand from cross, there is a --target-command flag which can be set to cross which will forward the feature flags to cross instead of cargo