You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When pushing tags, Travis CI automatically pushes a new release of the library to PyPI.
This is working correctly, but we are trying to push artifacts for every combination in our build matrix, which causes all builds in the matrix after the first to fail, since the release is already on PyPI.
This isn't actively harmful, since pushing artifacts to PyPI is the last step in the Travis CI test script, and we will separately test the master branch at the same time, but it would be nice to fix this.
The text was updated successfully, but these errors were encountered:
@azavea/operations This may also be an issue for other Azavea Python libraries that are published to PyPI, I believe we've been using a similar Travis CI configuration on other libraries.
I fixed this halfway as part of #112 but it looks like we need another environment variable check in addition to the Python version check, as Hector mentioned in the previous comment.
When pushing tags, Travis CI automatically pushes a new release of the library to PyPI.
This is working correctly, but we are trying to push artifacts for every combination in our build matrix, which causes all builds in the matrix after the first to fail, since the release is already on PyPI.
We should restrict our
deploy
step to only run once, if possible. Travis CI build stages might be helpful here: https://docs.travis-ci.com/user/build-stagesThis isn't actively harmful, since pushing artifacts to PyPI is the last step in the Travis CI test script, and we will separately test the
master
branch at the same time, but it would be nice to fix this.The text was updated successfully, but these errors were encountered: