Push Releases from CI

[SteadBytes]

To help avoid the problems with releasing experienced in the Flask-RESTPlus project. We should be able to make new releases to PyPi from CI - i.e. not relying on a core team member to release 'manually' from his/her own machine.

My initial proposal is that CI will push a release to PyPi when a release is tagged on GitHub. I haven't put a whole lot of thought into this as of yet so suggestions are more than welcome 😄

[callamd]

Yes; the tag should trigger a build and the resulting package should be pushed to pypy - it should also probably run tests before it gets to that point.

CI should be setup to run tests on PR's too.

Which tool should we use?

[ziirish]

CI is already up and running for PRs.

I'll have a look at how to build & push releases from travis to PyPi.

[SteadBytes]

@cal97g CI is already set up to run tests for PRs 😀 It’s using Travis CI as previously with Flask-RESTPlus #4

[ziirish]

Our first release has been automatically published on PyPi through travis-ci. I believe this issue is now resolved.