-
Notifications
You must be signed in to change notification settings - Fork 4
/
appveyor.yml
130 lines (118 loc) · 4.51 KB
/
appveyor.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
version: 1.3.{build}
branches:
only:
- master
- develop
# Rust needs at least Visual Studio 2013 image to build the MSVC targets.
image:
- Visual Studio 2019
# TODO: Add support for UUbuntu and macOS images.
# - Ubuntu
# - macOS
# This configuration will setup a build for each channel & target combination
# (8 windows combinations in all). You can add the `beta` channel to make all
# combinations. There are 2 channels here: stable and nightly.
#
# Alternatively, the full version may be specified for the channel to build
# using that specific version (e.g. channel: 1.5.0).
#
# The values for target are the set of windows Rust build targets.
# Each value is of the form:
#
# `ARCH-pc-windows-TOOLCHAIN`
#
# Where `ARCH` is the target architecture, either `x86_64` or `i686`, and
# `TOOLCHAIN` is the linker toolchain to use, either `msvc` or `gnu`.
#
# See <https://www.rust-lang.org/downloads.html#win-foot> for a description of
# the toolchain differences.
#
# See <https://github.com/rust-lang-nursery/rustup.rs/#toolchain-specification>
# for description of toolchains and host triples.
environment:
global:
# This will be used as part of the zipfile name.
PROJECT_NAME: sage
matrix:
# MSVC Toolchains
# Stable 64-bit MSVC
- channel: stable
target: x86_64-pc-windows-msvc
# Stable 32-bit MSVC
- channel: stable
target: i686-pc-windows-msvc
# Nightly 64-bit MSVC
- channel: nightly
target: x86_64-pc-windows-msvc
# Nightly 32-bit MSVC
- channel: nightly
target: i686-pc-windows-msvc
# GNU Toolchains
# Stable 64-bit GNU
- channel: stable
target: x86_64-pc-windows-gnu
# Stable 32-bit GNU
- channel: stable
target: i686-pc-windows-gnu
# Nightly 64-bit GNU
- channel: nightly
target: x86_64-pc-windows-gnu
# Nightly 32-bit GNU
- channel: nightly
target: i686-pc-windows-gnu
# This is the most important part of the Appveyor configuration. This installs
# the version of Rust specified by the `channel` and `target` environment
# variables from the "build matrix". This uses rustup to install Rust.
#
# For simple configurations, instead of using the build matrix, you can simply
# set the `default-toolchain` and `default-host` manually here.
install:
- appveyor DownloadFile https://win.rustup.rs/ -FileName rustup-init.exe
- rustup-init -yv --default-toolchain %channel% --default-host %target%
- set PATH=%PATH%;%USERPROFILE%\.cargo\bin
- rustc -vV
- cargo -vV
# See Appveyor documentation for specific details. In short, place any `channel`
# or `targets` you wish to allow build failures on (usually `nightly` at least
# is a wise choice). This will prevent a build or test failure in the matching
# channels/targets from failing the entire build.
matrix:
allow_failures:
- channel: nightly
# `cargo test` takes care of building for us, so disable Appveyor's build stage.
# This prevents the "directory does not contain a project or solution file" error.
build: false
# Uses `cargo test` to run tests and build. Alternatively, the project may call
# compiled programs directly or perform other testing commands. Rust will
# automatically be placed in the `PATH` environment variable.
test_script:
- cargo test --verbose --workspace --all-features
before_deploy:
# Generate artifacts for release.
- cargo build --release --workspace --all-features
- mkdir -p staging
- copy target/release/sage.exe staging
- cd staging
# Release zipfile will look like this: 'sage-v1.2.3-x86_64-pc-windows-msvc'
- 7z a ../%PROJECT_NAME%-%APPVEYOR_REPO_TAG_NAME%-%target%.zip *
- appveyor PushArtifact %PROJECT_NAME%-%APPVEYOR_REPO_TAG_NAME%-%target%.zip
deploy:
release: sage-v%APPVEYOR_BUILD_VERSION%
description: 'Windows release'
# All the zipped artifacts will be deployed.
artifact: /.*\.zip/
# TODO: Regenerate this auth_token for your project, this one won't work for you. Here's how:
# - Go to 'https://github.com/settings/tokens/new' and generate a Token with only the
# `public_repo` scope enabled.
# - Then go to 'https://ci.appveyor.com/tools/encrypt' and enter the newly generated token.
# - Copy the encrypted token and paste it here.
auth_token:
secure: Rnc9Fe+hxzJJiNUi0QpNm0euZC1y+6D3+RBmxzSmuauETzXYuD8paauAxvHYWeGm
provider: GitHub
# Deploy when a new tag is pushed and only on the stable channel.
on:
# Channel to use to produce the release artifacts.
# NOTE: Make sure you only release *once* per tag.
channel: stable
branch: master
APPVEYOR_REPO_TAG: true