forked from pytransitions/transitions
-
Notifications
You must be signed in to change notification settings - Fork 0
/
appveyor.yml
39 lines (32 loc) · 1.18 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
environment:
matrix:
# http://www.appveyor.com/docs/installed-software#python
- PYTHON: "C:\\Python27"
- PYTHON: "C:\\Python33"
- PYTHON: "C:\\Python34"
- PYTHON: "C:\\Python35"
- PYTHON: "C:\\Python36"
- PYTHON: "C:\\Python27-x64"
- PYTHON: "C:\\Python33-x64"
- PYTHON: "C:\\Python34-x64"
- PYTHON: "C:\\Python35-x64"
- PYTHON: "C:\\Python36-x64"
install:
- "%PYTHON%\\python.exe -m pip install -r requirements.txt"
- "%PYTHON%\\python.exe -m pip install -r requirements_test.txt"
build: off
test_script:
- "%PYTHON%\\python.exe -m nose --with-coverage --with-doctest"
#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
# - "%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.