forked from CADWRDeltaModeling/vtools
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathappveyor.yml
51 lines (43 loc) · 2.02 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
environment:
matrix:
# For Python versions available on Appveyor, see
# http://www.appveyor.com/docs/installed-software#python
# The list here is complete (excluding Python 2.6, which
# isn't covered by this document) at the time of writing.
- PYTHON: "C:\\Miniconda-x64"
PYTHON_VERSION: 2.7
PYTHON_ARCH: 64
install:
# We need wheel installed to build wheels
- "cd"
- "SET PATH=%PYTHON%;%PYTHON%\\Scripts;%PATH%"
- "python --version"
# - ps: Start-FileDownload 'https://msb.water.ca.gov/documents/86709/cfa0abab-5141-41ca-bde8-6a6eae5497ed' pydss_0.8_py2.7_amd64.exe
# - "msiexec /i c:\\Projects\\vtools\\pydss_0.8_py2.7_amd64.exe /quiet /qn /norestart /log c:\\install.log"
- "%PYTHON%\\Scripts\\conda install -y nose numpy scipy dateutil matplotlib"
build: off
test_script:
# Put your test command here.
# If you don't need to build C extensions on 64-bit Python 3.3 or 3.4,
# you can remove "build.cmd" from the front of the command, as it's
# only needed to support those cases.
# Note that you must use the environment variable %PYTHON% to refer to
# the interpreter you're using - Appveyor does not do anything special
# to put the Python version you want to use on PATH.
- "%PYTHON%\\Scripts\\nosetests -v --with-xunit"
- ps: |
$wc = New-Object 'System.Net.WebClient'
$wc.UploadFile("https://ci.appveyor.com/api/testresults/xunit/$($env:APPVEYOR_JOB_ID)", (Resolve-Path .\nosetests.xml))
after_test:
# This step builds your wheels.
# Again, you only need build.cmd if you're building C extensions for
# 64-bit Python 3.3/3.4. And you need to use %PYTHON% to get the correct
# interpreter
# - "build.cmd %PYTHON%\\python.exe setup.py bdist_wheel"
artifacts:
# bdist_wheel puts your built wheel in the dist directory
# - path: dist\*
#on_success:
# You can use this step to upload your artifacts to a public website.
# See Appveyor's documentation for more details. Or you can simply
# access your wheels from the Appveyor "artifacts" tab for your build.