Closed realcr closed 5 years ago
Looking at Travis rust.rb
, it appears it's using rust:
value just for TRAVIS_RUST_VERSION
and for rustup-init.sh
--default-toolchain
parameter.
When rustup-init.sh
is called with --default-toolchain=none
, it doesn't install any toolchains, but it does create cargo
and rustc
files that just print error: no default toolchain configured
unless they find rust-toolchain
file. So, setting rust: none
could be perfect for us.
TRAVIS_RUST_VERSION
is used only in cargo-sweep.sh
right now, and could easily be eliminated from there. We would just need to remember not to use it.
Alternatively, we could stop using Travis Rust integration. Then in our .travis.yml
we would need:
${TRAVIS_HOME}/.cargo/bin
added to $PATH
${TRAVIS_HOME}/.cargo
and target
added to cache settingsBy the way, it seems like we have redundant .cargo
caching settings in .travis.yml
right now. Seems harmless.
We currently have the pinned rust nightly version in use scattered in a few places. (1) The file:
rust-toolchain
(See here: https://github.com/rust-lang/rustup.rs#the-toolchain-file) (2) .travis.yml contains the used nightly version in three places (See snippet below).This means that every time we bump rust nightly's version we have to modify all those places at the same time. Is it somehow possible for us to make .travis.yml find the pinned rust nightly version from the
rust-toolchain
file automatically?Snippet from
.travis.yml
(Containing rust nightly version 3 times):EDIT: See: https://github.com/travis-ci/travis-build/pull/1513