Update PyPi credentials #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rbreslow
commented
Apr 10, 2019
rbreslow
commented
Apr 10, 2019
hectcastro
approved these changes
Apr 10, 2019
rbreslow
added a commit
that referenced
this pull request
Apr 10, 2019
* Update PyPi credentials * Try authentication against test.pypi.org * Apply suggestions from code review * Restore comments * fixup! Restore comments
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
I was able to get a deploy to PyPi to go through using the credentials in this PR.
I did what you suggested, which was to run
$ travis setup pypi. At first, this didn't work. I did it again, this time specifying--repo. The second time it worked.$ travis setup pypi --force ---repo "azavea/django-ecsmanage"¯_(ツ)_/¯
Testing Instructions
See that the CI checks below are failing, but due to invalid version metadata (this isn't a tagged release). If the credentials were broken, we'd be seeing a 4XX authentication error.