Files
libloot-python/appveyor.yml
T
Oliver Hamlet 9a21830bd6 Remove CTest usage
It behaves differently when run from MSVC and the command line, and
doesn't display test output unless an env var or CLI flag is set, so
it's better just to run the Python script directly.
2016-09-18 18:18:08 +01:00

43 lines
1.1 KiB
YAML

os: Visual Studio 2015
version: "{build}-{branch}"
configuration: Release
before_build:
- cd %APPVEYOR_BUILD_FOLDER%
- ps: mkdir build
- cd build
- cmake .. -G "Visual Studio 14 2015"
build:
verbosity: minimal
project: 'c:\projects\loot-api-python\build\loot_api_python.sln'
test_script:
- cd %APPVEYOR_BUILD_FOLDER%\build\Release
- python -m unittest test
after_test:
- cd %APPVEYOR_BUILD_FOLDER%\build
- cpack
# AppVeyor checks out a specific commit, but that means the archive script
# can't tell which branch it's on, so rename the 7z archives.
- ps: $env:GIT_DESCRIBE = ((git describe --tags --long --always) | Out-String) -replace "`n|`r", ""
artifacts:
- path: build\package\loot_api_python-$(GIT_DESCRIBE)-win32.7z
name: loot_api_python
deploy:
- provider: BinTray
username: wrinklyninja
api_key:
secure: u234T2688DZmz4JH5+0iAHcUcL2fEIGculb8655bn4B1q7GckhplsitzgEbv3NFc
subject: wrinklyninja
repo: loot
package: loot-api-python
version: $(GIT_DESCRIBE)_$(APPVEYOR_REPO_BRANCH)
publish: true
artifact: loot_api_python