Skip to content

Commit 008e5dc

Browse files
committedNov 13, 2018
appveyor: Use VS2017 for all our images
This was [recommended by AppVeyor][1] to see if it has any impact on our build times, hopefully on the beneficial side of things! This shouldn't affect our binary compatibility for generated compilers like it would normally do for Linux. [1]: https://help.appveyor.com/discussions/questions/29832-did-recent-changes-apply-to-possibly-slow-down-builds#comment_46484879

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed
 

‎appveyor.yml

+4-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
11
environment:
2-
SCCACHE_DIGEST: f808afabb4a4eb1d7112bcb3fa6be03b61e93412890c88e177c667eb37f46353d7ec294e559b16f9f4b5e894f2185fe7670a0df15fd064889ecbd80f0c34166c
2+
# This is required for at least an AArch64 compiler in one image, and is
3+
# otherwise recommended by AppVeyor currently for seeing if it has any
4+
# affect on our job times.
5+
APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017 Preview
36

47
# By default schannel checks revocation of certificates unlike some other SSL
58
# backends, but we've historically had problems on CI where a revocation
@@ -82,7 +85,6 @@ environment:
8285
DIST_REQUIRE_ALL_TOOLS: 1
8386
DEPLOY: 1
8487
CI_JOB_NAME: dist-x86_64-msvc
85-
APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017 Preview
8688
- RUST_CONFIGURE_ARGS: >
8789
--build=i686-pc-windows-msvc
8890
--target=i586-pc-windows-msvc

0 commit comments

Comments
 (0)
Please sign in to comment.