[Numpy-discussion] Daily numpy wheel builds - prefer to per-commit builds?
matthew.brett at gmail.com
Tue Feb 28 03:43:47 EST 2017
I've been working to get daily travis-ci cron-job manylinux builds
working for numpy and scipy wheels. They are now working OK:
These are daily builds of the respective numpy and scipy master branches.
Numpy already has a system, kindly worked up by Olivier Grisel, which
uploads wheel builds from each travis-ci run. travis-ci uploads these
wheels for every commit, at the
"travis-dev-wheels" container on Rackspace, visible at
. These builds are specific to the Linux they were built on - in this
case Ubuntu 12.04.
Some projects use these per-commit builds for testing compatibility
with development Numpy code.
Now I'm wondering what the relationship should be between the current
every-commit builds and the new wheel builds.
I think that we should prefer the new wheel builds and deprecate the
previous per-commit builds, because:
* the new manylinux wheels are self-contained, and so can be installed
with pip without extra lines of `apt` installs;
* the manylinux builds work on any travis container, not just the current
* manylinux builds should be faster, as they are linked against OpenBLAS;
* manylinux wheels are closer to the wheels we distribute for
releases, and therefore more useful for testing against.
What do y'all think?
More information about the NumPy-Discussion