Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Python] Create single external GitHub repo building for building wheels for all platforms in one shot #16711

Closed
asfimport opened this issue Jun 13, 2017 · 4 comments

Comments

@asfimport
Copy link

asfimport commented Jun 13, 2017

  • manylinux1 (for Linux)
  • macOS
  • Windows

We have all the machinery to do this, but we need to set things up to upload to a single BinTray location

https://github.com/xhochy/pyarrow-macos-wheels
https://github.com/wesm/pyarrow-windows-wheels

Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney / @wesm

Related issues:

Note: This issue was originally created as ARROW-1116. Please see the migration documentation for further details.

@asfimport
Copy link
Author

Uwe Korn / @xhochy:
As Appveyor, Travis and BinTray are available as services that we can get activated via Infra, we could make this part of the official release and also vote on them as part of the release vote as we do currently with the Java jars. I would then suggest to have an additional ASF git repo for the wheels. This would avoid a lot of issues with clearly declaring them "unofficial".

Only the base images for the manylinux1 docker image is on quay.io which probably won't become available via Infra due to permissions it wants on the repo. For now, this should be okay.

@asfimport
Copy link
Author

Wes McKinney / @wesm:
Seems reasonable to me. We can create an arrow-dist repo for this purpose

@asfimport
Copy link
Author

Uwe Korn / @xhochy:
Moving this to 0.6.0 as we have to wait a bit for Infra to set up all necessary things.

@asfimport
Copy link
Author

Wes McKinney / @wesm:
I think we took this as far as we can around 0.6.0 time. We cannot get arrow-dist to directly upload to the apache BinTray, so currently it is uploading to wesm/apache-arrow-test. I have been unable to get an encrypted upload key under the Apache Appveyor account, so what I did for 0.6.0 was pushed to my fork wesm/arrow-dist and the Appveyor build uploaded from there also to wesm/apache-arrow-test on BinTray. I think this is adequate for the next few releases. I will be happy to give push privileges or other administrative rights on my forks or BinTray projects so that others can build the packages, too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants