kiwitcms / tcms-api

65%

master: 65%

LAST BUILD ON BRANCH build_wheels_on_windows

branch: build_wheels_on_windows

CHANGE BRANCH

x

Reset

• build_wheels_on_windows
• everything_wo_gssapi
• kerberos_fix
• master
• next_release
• plugin8
• pr14
• test_on_windows
• test_with_kerberos
• use_new_api
• v6.7
• v6.7.1
• v8.0
• v8.0.1
• windows_ci
• workaround2

Build # 234

Build Type

Pull #27

travis-ci

Committed by web-flow

Commit Message

Start building packages on Windows. Fix #3

NOTE: the wheel package itself is a pure-python package so it
will not matter on what OS it has been built! With the latest
changes to use winkerberos over kerberos customers should be able
to pip install directly on any operating system and pip will
resolve the dependencies for them.

- Prepend C:\cygwin64\bin to PATH
- Prepend C:\Users\appveyor\AppData\Roaming\Python\Python36\Scripts
  to PATH (for wheel.exe)
- unpack wheel packages instead of using unzip -t b/c in AppVeyor
  cygwin64 doesn't have unzip and the one which is in PATH fails
- Use the default Python executable when building venvs for testing
- Replace "bin/activate" with "Scripts/activate" via sed
- Remove "pip install kerberos" b/c winkerberos ships both Source and
  Whell packages
- Remove "-p $(which python)" when calling virtualenv b/c it fails. In
  AppVeyor we have C:\Python36-x64\Scripts\virtualenv.exe in PATH
- Start keeping the built artifacts on AppVeyor

Pull Request Pull Request #27: Build wheels on windows

Run Details

139 of 214 relevant lines covered (64.95%)

0.65 hits per line