-
Notifications
You must be signed in to change notification settings - Fork 20
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
issue with pypi deployment #28
Comments
In googling to fix this for my own repository, I came across your issue. I believe this is due to the build artifacts getting "cleaned" in the "Preparing deploy" step in Travis just before they are deployed to PyPi in the "Deploy Application" step directly after. The remedy, I found is to add Below is from your build found here: https://travis-ci.org/amey-sam/Flask-MailGun/jobs/460912350 Also, since your Travis build has multiple version builds, each one will try to deploy your application. The first one to finish will succeed but all others after will fail on the PyPi side with "version already exists" type error. Thus, will also need the |
PyPI deployment failed with the following error in the Travis log https://travis-ci.com/manubot/manubot/jobs/176983327#L1104): ``` Could not restore untracked files from stash entry PyPI upload failed. failed to deploy ``` skip_cleanup documentation from https://docs.travis-ci.com/user/deployment/pypi/#releasing-build-artifacts > After your tests ran and before the release, Travis CI will clean up any additional files and changes you made. Maybe that is not what you want, as you might generate some artifacts that are supposed to be released, too. See also: - amey-sam/MIGRATED-Flask-MailGun#28 (comment)
PyPI deployment failed with the following error in the Travis log https://travis-ci.com/manubot/manubot/jobs/176983327#L1104: ``` Could not restore untracked files from stash entry PyPI upload failed. failed to deploy ``` skip_cleanup documentation from https://docs.travis-ci.com/user/deployment/pypi/#releasing-build-artifacts > After your tests ran and before the release, Travis CI will clean up any additional files and changes you made. Maybe that is not what you want, as you might generate some artifacts that are supposed to be released, too. See also: - amey-sam/MIGRATED-Flask-MailGun#28 (comment)
Errors in part due to multiple Python versions (which tries to upload to PyPI for each version). See: - amey-sam/MIGRATED-Flask-MailGun#28 - amey-sam/MIGRATED-Flask-MailGun#29
FaradayRF/faradayio#35
travis-ci/travis-ci#10056
The text was updated successfully, but these errors were encountered: