appveyor.yml
environment:
matrix:
# For Python versions available on Appveyor, see
# http://www.appveyor.com/docs/installed-software#python
- PYTHON: "C:\\Python36"
- PYTHON: "C:\\Python37-x64"
cache:
- "%LOCALAPPDATA%\\pip\\Cache -> appveyor.yml" # Use cache unless appveyor.yml changes.
- "tests\\data -> appveyor.yml"
- "data\\ -> appveyor.yml"
- "tests\\data -> appveyor.yml"
install:
- SET PATH=%PYTHON%;%PYTHON%\Scripts\;%path%
# - "%PYTHON%\\python.exe -m pip install --upgrade pip"
# We need wheel installed to build wheels
- "%PYTHON%\\python.exe -m pip install wheel"
-
- "%PYTHON%\\python.exe -m pip install -r requirements_dev.txt"
- "%PYTHON%\\python.exe -m pip install -r requirements.txt"
# Installing eniric now
- "%PYTHON%\\python.exe -m pip install -e .[dev,test,docs,ci]"
# Setup config and make data
# This is not the best place to put this but before_test didn't work.
# - cmd: "move tests\\config.yaml config.yaml"
# Downloading Eniric data with powershell script for windows
- ps: ".\\scripts\\download\\ps_download_eniric_data.ps1"
# Prepare atmosphere models
- cmd: "%PYTHON%\\python.exe scripts\\split_atmmodel.py -b ALL"
- cmd: "%PYTHON%\\python.exe scripts\\barycenter_broaden_atmmodel.py -b ALL"
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.
- cmd: "%PYTHON%\\python.exe -m pytest --cov=. --cov-report term-missing --durations 10"
- cmd: "%PYTHON%\\python.exe -m coverage xml -i"
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.
matrix:
fast_finish: true