Provide a built-in way for rustup to adapt to a CI environment
Open
@rami3l is already working on this.
Since Aug 17, 2026.
enhancement
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Discussed at the rust all-hands, it was suggested that it'd be good if rustup had better support for CI scenarios so it's less necessary for people to rely on third parties to provide them. This issue is intended to explore the existing options and see what we can adopt into rustup itself and how we can do so.
The most current github actions for rustup are rust-toolchain and setup-rust-toolchain.
What the actions do
- sets environment variables by default such as:
CARGO_UNSTABLE_SPARSE_REGISTRY=trueCARGO_REGISTRIES_CRATES_IO_PROTOCOL=sparse(or=gitfor older cargo)CARGO_INCREMENTAL=0CARGO_PROFILE_DEV_DEBUG=0RUST_BACKTRACE=shortCARGO_TERM_COLOR=always
- runs
rustup toolchain installto install the current default toolchain - Uses
--profile minimaland--no-self-updatewhen installing specified toolchains - provides problem matchers for cargo and rustfmt issues
They can also provide caching but that is deemed out of scope for rustup.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.