-
Notifications
You must be signed in to change notification settings - Fork 237
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
Would it be possible to deploy to pypi automatically from travis? #4
Comments
Yes that's possible, just make sure that you get your deploy rules set up right so you're not always trying to overwrite each version! I think PyPI won't overwrite existing wheels for each release. |
I've added some deploy commands to my travis file, and my build succeeds, but it doesn't look like the wheels are being uploaded to pypi. What do you think? My guess is it has to do with the deployer being confused at already finding wheels in |
In the macOS build, something different happened, which made me think it might be the version number. I've upped the version number and I'm trying again. |
@joerick After updating the version number to |
Hey! I think you might need the I've not added this to the docs because in the past I've found it really hard to get this kind of auto-deploy mechanism to work satisfactorily - for example, normally you'd set it to only deploy on a tag but say the build fails, then you've got to tag/release a whole new version just to fix the build. Also, you have to upload the sdist separately, but the wheel uploads will lag so some users will get sdist just because the wheel is still building. Sorry to be negative! I'm sure there's a good way to do it but I'm not ready to recommend anything yet! So for now my recommended method is a temporary storage location and a manual deploy. Do let me know if this works well for you though, it might become a case study for others to use. 👍 |
Thanks as always for getting back to me @joerick. Apologies for being such a noob, but I have a few questions about this:
but I'm not sure in my current config where I'm even putting my wheels. My mental model for travis is that it's spinning up a VM, doing all these tasks, then throwing away all the data and reporting back whether it succeeded. It's putting all the wheels in
|
Check out these travis docs. I'm probably wrong, but would it be possible to upload these wheels directly, in the same step?
The text was updated successfully, but these errors were encountered: