https://github.com/sethmlarson/python-travis-deploy

A test project for deploying to PyPI from Travis
https://github.com/sethmlarson/python-travis-deploy

pypi python travis-ci twine

Last synced: 3 months ago
JSON representation

A test project for deploying to PyPI from Travis

• Host: GitHub
• URL: https://github.com/sethmlarson/python-travis-deploy
• Owner: sethmlarson
• License: apache-2.0
• Created: 2018-12-08T21:27:05.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2018-12-09T02:37:37.000Z (over 6 years ago)
• Last Synced: 2025-01-18T16:20:37.509Z (4 months ago)
• Topics: pypi, python, travis-ci, twine
• Language: Python
• Size: 25.4 KB
• Stars: 1
• Watchers: 1
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.rst
  • License: LICENSE

Awesome Lists containing this project

README

        
Python Travis Deploy

====================

A test project for deploying to PyPI from Travis

Deployment Strategy

-------------------

- Any user can create a new branch and commits that puts the package

  into a deployable state. (Updating changelog, putting release date, etc)

  The branch must be named ``release-x.x.x`` to trigger integration tests

- User creates a Pull Request to the repo as normal.

- Travis runs unit tests as normal.

- Travis runs integration tests due to the ``release-x.x.x`` branch name.

- Once merged any maintainer can tag the squashed commit and push tags to GitHub.

- Travis will build and deploy the tagged commit and upload to PyPI.

- Travis will prepare a GitHub release draft for the tag.

- Once you're satisfied with the release content (ie changelog entry info)

  you can publish the release.

Configuration Options

---------------------

- If your deployment uses universal wheels you can consolidate the

  two PyPI deployments into one and build both within ``_travis/deploy.sh``.

- If you're not a fan of GitHub releases you can remove that section

  within ``deploy:`` in ``.travis.yml``.