Skip to content
This repository was archived by the owner on Aug 30, 2024. It is now read-only.

DOC: Update README.rst #83

Merged
merged 1 commit into from
May 4, 2020
Merged

DOC: Update README.rst #83

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 23 additions & 12 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,20 +3,31 @@ Building and uploading numpy wheels
###################################

The wheel builds are currently done by Azure Pipelines. Options that may be
used for future builds are Travis CI and Appveyor. The progress and success of
builds may be monitored at the following locations:
used for future builds are TravisCI and Appveyor. Note that currently TravisCI
and Appveyor are not triggered, if you want to enable them you will need to do
so in the settings/Webhooks.

Azure Pipelines at
https://dev.azure.com/numpy/numpy/_build?definitionId=8&_a=summary&view=runs
**Build process pages**

Travis CI at
https://travis-ci.org/MacPython/numpy-wheels
- Azure Pipelines at
https://dev.azure.com/numpy/numpy/_build?definitionId=8&_a=summary&view=runs

The Appveyor at
https://ci.appveyor.com/project/matthew-brett/numpy-wheels
- Travis CI at
https://travis-ci.org/MacPython/numpy-wheels

The driving github repository is
https://github.com/MacPython/numpy-wheels
- The Appveyor at
https://ci.appveyor.com/project/matthew-brett/numpy-wheels

- The driving github repository is
https://github.com/MacPython/numpy-wheels

**Uploaded file locations**

- Release builds at
https://anaconda.org/multibuild-wheels-staging/numpy/files
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just noticed that the 1.18.4 wheels there still have .dev0 in the name, so is it also triggered for non-release builds?

Copy link
Contributor Author

@charris charris May 4, 2020 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, those wheels shouldn't be there and need to be removed. I think they have been triggered by merges to the master branch as the azure configuration currently points to the HEAD of the 1.18.x branch. We probably need to configure the pipeline not to upload on merges as that makes it hard to work on the repo. We should also configure things so that master uploads to the nightly directory when triggered directly.

I think @mattip has permissions to delete those files. We should probably get permissions for a few more folks to raise the bus factor.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll go ahead and point the master branch to master and see if that makes a difference.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also don't know who owns the Azure integration here, I don't see the usual option to remove it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now it is building master but still uploading to the wrong directory when triggerd, so that needs fixing. The directory should be made to depend on the branch.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you both have anaconda.org accounts/monikers I can add to admin there?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do have permissions to remove the files, but probably best to give you both access anyway. I'll check back later.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have an account as charlesr.harris.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright, you have admin there now


- Nightly builds at
https://anaconda.org/scipy-wheels-nightly/numpy/files


How it works
Expand Down Expand Up @@ -86,7 +97,7 @@ You will typically have a directory on your machine where you store wheels,
called a `wheelhouse`. The typical call for `wheel-uploader` would then
be something like::

CDN_URL=https://anaconda.org/multibuild-wheels/staging/numpy/files
CDN_URL=https://anaconda.org/multibuild-wheels-staging/numpy/files
wheel-uploader -r warehouse -u $CDN_URL -s -v -w ~/wheelhouse -t macosx numpy 1.19.0
wheel-uploader -r warehouse -u $CDN_URL -s -v -w ~/wheelhouse -t manylinux1 numpy 1.19.0
wheel-uploader -r warehouse -u $CDN_URL -s -v -w ~/wheelhouse -t win numpy 1.19.0
Expand All @@ -106,7 +117,7 @@ where:
``1.19.0`` is the version to download / upload.

So, in this case, ``wheel-uploader`` will download all wheels starting with ``numpy-1.19.0-``
from https://anaconda.org/multibuild-wheels/staging/numpy/files to ``~/wheelhouse``,
from https://anaconda.org/multibuild-wheels-staging/numpy/files to ``~/wheelhouse``,
then upload them to PyPI.

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