source: trunk/.appveyor.yml

Last change on this file was 9da5194, checked in by Jean-Paul Calderone <exarkun@…>, at 2020-01-20T18:27:41Z

coverage wants to play

this is another instance of the 5.0 incompatibility

  • Property mode set to 100644
File size: 3.1 KB
Line 
1# adapted from https://packaging.python.org/en/latest/appveyor/
2
3environment:
4
5  matrix:
6
7    # For Python versions available on Appveyor, see
8    # http://www.appveyor.com/docs/installed-software#python
9    - PYTHON: "C:\\Python27"
10    - PYTHON: "C:\\Python27-x64"
11    #  DISTUTILS_USE_SDK: "1"
12    #  TOX_TESTENV_PASSENV: "DISTUTILS_USE_SDK INCLUDE LIB"
13
14install:
15  - |
16    %PYTHON%\python.exe -m pip install -U pip
17    %PYTHON%\python.exe -m pip install wheel tox==3.9.0 virtualenv
18
19# note:
20# %PYTHON% has: python.exe
21# %PYTHON%\Scripts has: pip.exe, tox.exe (and others installed by bare pip)
22
23# We have a custom "build" system.  We don't need MSBuild or whatever.
24build: off
25
26# Do not build feature branch with open pull requests.  This is documented but
27# it's not clear it does anything.
28skip_branch_with_pr: true
29
30# This, perhaps, is effective.
31branches:
32  # whitelist
33  only:
34    - 'master'
35
36skip_commits:
37 files:
38   # The Windows builds are unaffected by news fragments.
39   - 'newsfragments/*'
40   # Also, all this build junk.
41   - '.circleci/*'
42   - '.lgtm.yml'
43   - '.travis.yml'
44
45# we run from C:\projects\tahoe-lafs
46
47test_script:
48  # Put your test command here.
49  # Note that you must use the environment variable %PYTHON% to refer to
50  # the interpreter you're using - Appveyor does not do anything special
51  # to put the Python version you want to use on PATH.
52  - |
53    %PYTHON%\Scripts\tox.exe -e coverage
54    %PYTHON%\Scripts\tox.exe -e pyinstaller
55  # To verify that the resultant PyInstaller-generated binary executes
56  # cleanly (i.e., that it terminates with an exit code of 0 and isn't
57  # failing due to import/packaging-related errors, etc.).
58  - dist\Tahoe-LAFS\tahoe.exe --version
59
60after_test:
61  # This builds the main tahoe wheel, and wheels for all dependencies.
62  # Again, you only need build.cmd if you're building C extensions for
63  # 64-bit Python 3.3/3.4. And you need to use %PYTHON% to get the correct
64  # interpreter. If _trial_temp still exists, the "pip wheel" fails on
65  # _trial_temp\local_dir (not sure why).
66  - |
67    copy _trial_temp\test.log trial_test_log.txt
68    rd /s /q _trial_temp
69    %PYTHON%\python.exe setup.py bdist_wheel
70    %PYTHON%\python.exe -m pip wheel -w dist .
71  - |
72    %PYTHON%\python.exe -m pip install codecov "coverage ~= 4.5"
73    %PYTHON%\python.exe -m coverage xml -o coverage.xml -i
74    %PYTHON%\python.exe -m codecov -X search -X gcov -f coverage.xml
75
76artifacts:
77  # bdist_wheel puts your built wheel in the dist directory
78  # "pip wheel -w dist ." puts all the dependency wheels there too
79  # this gives us a zipfile with everything
80  - path: 'dist\*'
81  - path: trial_test_log.txt
82    name: Trial test.log
83  - path: eliot.log
84    name: Eliot test log
85
86on_failure:
87  # Artifacts are not normally uploaded when the job fails.  To get the test
88  # logs, we have to push them ourselves.
89  - ps: Push-AppveyorArtifact _trial_temp\test.log -Filename trial.log
90  - ps: Push-AppveyorArtifact eliot.log -Filename eliot.log
91
92#on_success:
93#  You can use this step to upload your artifacts to a public website.
94#  See Appveyor's documentation for more details. Or you can simply
95#  access your wheels from the Appveyor "artifacts" tab for your build.
Note: See TracBrowser for help on using the repository browser.