This project has been archived by its maintainers, and is no longer receiving any updates.
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.
Metadata
Release files for python-travis-deploy 1.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| python_travis_deploy-1.5.0.tar.gz | 6.0 kB | Without provenance | Details for python_travis_deploy-1.5.0.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| python_travis_deploy-1.5.0-py3-none-any.whl | Python 3 | none | any | Details for python_travis_deploy-1.5.0-py3-none-any.whl |
| python_travis_deploy-1.5.0-py2-none-any.whl | Python 2 | none | any | Details for python_travis_deploy-1.5.0-py2-none-any.whl |
Total release size: 18.6 kB
Release files / python_travis_deploy-1.5.0.tar.gz
| Download URL | python_travis_deploy-1.5.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7ad6cf92f0c56df78bfdc2fe511d42a7cf1bc048e9636216263f78494a803c0
|
|
BLAKE2b-256 checksum How to use checksums |
92d2851a6dacb7f5fcba38b60b3c56d01d27534b1a62d48597748345f5f44b0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.3
|
Release files / python_travis_deploy-1.5.0-py3-none-any.whl
| Download URL | python_travis_deploy-1.5.0-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
642cdcebf64414caacad7bd61790cf294e2e3d8d5da6f12921165c50dd727758
|
|
BLAKE2b-256 checksum How to use checksums |
3fd9e10e03fcd88ad25bff9977d1877d8f7208c7b7c38f7fd21a328f5e5112a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.3
|
Release files / python_travis_deploy-1.5.0-py2-none-any.whl
| Download URL | python_travis_deploy-1.5.0-py2-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
deba70bab661ca812b0899f76aec7c6b15e70fc276af63ff3f5f9504d22fd6cc
|
|
BLAKE2b-256 checksum How to use checksums |
cf00ab04f66f199d2deb851178a2c84f708a7825bf76357d585fee5ddbcbc8f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/2.7.14
|
Security for python-travis-deploy 1.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.