rust/appveyor.yml
Philipp Hansch 8d7a5fe126
Only run AppVeyor on r+, try and the master branch
As it is right now, there is only one worker available in the `rust-lang-libs`
AppVeyor project and there are other repos as well that we share this worker
with. This has been a problem for us because we sometimes hit a bors timeout if there
are too many builds queued up.

To improve the situation, I think we could try to use AppVeyor a bit less
often. The average PR is not going to break windows related things anyway, so
it should be fine to run it on r+/try/master only.
2019-04-24 20:25:59 +02:00

41 lines
1.2 KiB
YAML

environment:
global:
PROJECT_NAME: rust-clippy
matrix:
#- TARGET: i686-pc-windows-gnu
#- TARGET: i686-pc-windows-msvc
#- TARGET: x86_64-pc-windows-gnu
- TARGET: x86_64-pc-windows-msvc
branches:
# Only build AppVeyor on r+, try and the master branch
only:
- auto
- try
- master
install:
- curl -sSf -o rustup-init.exe https://win.rustup.rs/
- rustup-init.exe -y --default-host %TARGET% --default-toolchain nightly
- set PATH=%PATH%;C:\Users\appveyor\.cargo\bin
- git ls-remote https://github.com/rust-lang/rust.git master | awk '{print $1}' >rustc-hash.txt
- set /p RUSTC_HASH=<rustc-hash.txt
- del rust-toolchain
- cargo install rustup-toolchain-install-master --debug || echo "rustup-toolchain-install-master already installed"
- rustup-toolchain-install-master %RUSTC_HASH% -f -n master
- rustup default master
- set PATH=%PATH%;C:\Users\appveyor\.rustup\toolchains\master\bin
- rustc -V
- cargo -V
build: false
test_script:
- set RUST_BACKTRACE=1
- cargo build --features debugging
- cargo test --features debugging
notifications:
- provider: Email
on_build_success: false