appveyor: put build steps in a script, rather than inline in appveyor.yml
[mesa.git] / appveyor.yml
1 # http://www.appveyor.com/docs/appveyor-yml
2 #
3 # To setup AppVeyor for your own personal repositories do the following:
4 # - Sign up
5 # - Add a new project
6 # - Select Git and fill in the Git clone URL
7 # - Setup a Git hook as explained in
8 # https://github.com/appveyor/webhooks#installing-git-hook
9 # - Check 'Settings > General > Skip branches without appveyor.yml'
10 # - Check 'Settings > General > Rolling builds'
11 # - Setup the global or project notifications to your liking
12 #
13 # Note that kicking (or restarting) a build via the web UI will not work, as it
14 # will fail to find appveyor.yml . The Git hook is the most practical way to
15 # kick a build.
16 #
17 # See also:
18 # - http://help.appveyor.com/discussions/problems/2209-node-grunt-build-specify-a-project-or-solution-file-the-directory-does-not-contain-a-project-or-solution-file
19 # - http://help.appveyor.com/discussions/questions/1184-build-config-vs-appveyoryaml
20
21 version: '{build}'
22
23 branches:
24 except:
25 - /^travis.*$/
26
27 # Don't download the full Mesa history to speed up cloning. However the clone
28 # depth must not be too small, otherwise builds might fail when lots of patches
29 # are committed in succession, because the desired commit is not found on the
30 # truncated history.
31 #
32 # See also:
33 # - https://www.appveyor.com/blog/2014/06/04/shallow-clone-for-git-repositories
34 clone_depth: 100
35
36 # https://www.appveyor.com/docs/build-cache/
37 cache:
38 - '%LOCALAPPDATA%\pip\Cache -> appveyor.yml'
39 - win_flex_bison-2.5.15.zip
40 - llvm-5.0.1-msvc2017-mtd.7z
41
42 os: Visual Studio 2017
43
44 init:
45 # Appveyor defaults core.autocrlf to input instead of the default (true), but
46 # that can hide problems processing CRLF text on Windows
47 - git config --global core.autocrlf true
48
49 environment:
50 WINFLEXBISON_VERSION: 2.5.15
51 LLVM_ARCHIVE: llvm-5.0.1-msvc2017-mtd.7z
52
53 install:
54 - call scripts\appveyor_msvc.bat install
55
56 build_script:
57 - call scripts\appveyor_msvc.bat build_script
58
59 after_build:
60 - call scripts\appveyor_msvc.bat after_build
61
62 # It's possible to setup notification here, as described in
63 # http://www.appveyor.com/docs/notifications#appveyor-yml-configuration , but
64 # doing so would cause the notification settings to be replicated across all
65 # repos, which is most likely undesired. So it's better to rely on the
66 # Appveyor global/project notification settings.