bashtage / arch-wheels

Wheel builder for arch releases

Building and uploading arch wheels

We automate wheel building using this custom github repository that builds on the travis-ci OSX machines and the travis-ci Linux machines.

The travis-ci interface for the builds is https://travis-ci.org/bashtage/arch-wheels

The driving github repository is https://github.com/bashtage/arch-wheels

How it works

The wheel-building repository:

• builds a arch wheel;
• processes the wheel using delocate (OSX) or auditwheel repair (Manylinux1). delocate and auditwheel copy the required dynamic libraries into the wheel and relinks the extension modules against the copied libraries;
• uploads the built wheels to http://test.pypi.org.

The resulting wheels are therefore self-contained and do not need any external dynamic libraries apart from those provided as standard by OSX / Linux as defined by the manylinux1 standard.

The .travis.yml file in this repository has a line containing the login for Test PyPi encrypted with an RSA key that is unique to the repository - see http://docs.travis-ci.com/user/encryption-keys. This encrypted key gives the travis build permission to upload to test PyPi.

Triggering a build

You will likely want to edit the .travis.yml file to specify the BUILD_COMMIT before triggering a build - see below.

You can trigger a build by:

• making a commit to the arch-wheels repository (e.g. with git commit --allow-empty); or
• clicking on the circular arrow icon towards the top right of the travis-ci page, to rerun the previous build.

In general, it is better to trigger a build with a commit, because this makes a new set of build products and logs, keeping the old ones for reference. Keeping the old build logs helps us keep track of previous problems and successful builds.

Which arch commit does the repository build?

The arch-wheels repository will build the commit specified in the BUILD_COMMIT at the top of the .travis.yml file. This can be any naming of a commit, including branch name, tag name or commit hash.

Uploading the built wheels to pypi

Wheels are are automatically uploaded using twine.

Of course, you will need permissions to upload to PyPI, for this to work.

Releasing

1. Run git submodule update --remote --merge
2. Search and replace previous version with current (e.g., 4.4.1 -> 4.5.0)
3. Build travis and appveyor without uploading to PyPi (see to False)
4. Build and upload to test and conda (set these to True, PyPi to False)
5. Build and upload to PyPi (set test and conda to False)