Closed sophiafarrell closed 2 years ago
How do we change to .com?
My only guess is that we need to change the TWINE info to route to .com. I think you did this recently (2019-2020).
Done, this is now over to .com.
Actually, this issue persists but now in a different form. The linux builds are still failing even with .com, due to us not having adequate quotas for Docker. Example of failed test here Link the test spits out upon failing here. @tunnell, Greg and I believe the fastest, but most expensive way, to solve this problem is to upgrade our travis-associated account of Docker to Docker Pro. Alternatively, can you suggest a different method of testing our linux builds?
Fixed via #86.
See: https://travis-ci.org/github/NESTCollaboration/nestpy/jobs/773401061
Issue: the Docker quota is met. This could potentially be fixed by our migrating over to travis-ci.com, which we already pay for. I believe this means we need to update our twine details in the travis.yml file.
Tagging @grischbieter and @tunnell for more feedback on this.