git-release-tagger
by Swing Development
Small CLI utility to enable the CI environment to communicate the deployment progress through the use of git tags.
Installation
$ pip install git-release-tagger
Usage
$ tag-release [-h] [-t TRIGGER] [-v] [-m MESSAGE]
prefix {pending,deploying,failed,success}
Prefix is self explanatory.
If the release was triggered by a tag (like ‘release’) - use the –trigger option to have the tagger remove it automatically. This enables the user to retry a failed deployment just by tagging the same commit again.
Use -m to add a message to the commit. For example - a link to the build status on Jenkins / TeamCity / other CI.
Examples
$ tag-release production pending
- will remove tags:
‘production_pending’,
‘production_deploying’,
‘production_failed’,
‘production_success’
- will add tags:
‘production_pending’
$ tag-release production success
- will remove tags:
‘production_pending’,
‘production_deploying’,
‘production_failed’,
‘production_success’
- will add tags:
‘production_success’
‘production_success_2015-11-02_16_34_26’
$ tag-release -t production production success
- will remove tags:
‘production’
‘production_pending’,
‘production_deploying’,
‘production_failed’,
‘production_success’
- will add tags:
‘production_success’
‘production_success_2015-11-02_16_34_26’
Release History
0.0.2 (2016-03-09)
‘git push’ is run with –no-verify to skip pre-push hooks.
0.0.1 (2015-11-03)
Initial release.
Metadata
Release files for git-release-tagger 0.0.2
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 |
|---|---|---|---|---|
| git-release-tagger-0.0.2.tar.gz | 4.7 kB | Without provenance | Details for git-release-tagger-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| git_release_tagger-0.0.2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for git_release_tagger-0.0.2-py2.py3-none-any.whl |
Total release size: 10.7 kB
Release files / git-release-tagger-0.0.2.tar.gz
| Download URL | git-release-tagger-0.0.2.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
228a9060c499cef1ccb1621ddfadd7cd15d4acfd1929720d01a5f7353c01a478
|
|
BLAKE2b-256 checksum How to use checksums |
0a89d96470316c1e9ef60e58616d3978cd7f87f49c936862a640a441123f6068
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / git_release_tagger-0.0.2-py2.py3-none-any.whl
| Download URL | git_release_tagger-0.0.2-py2.py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b09b95eb333e6d126764a90349797d8d7ea009c5d52f2ae588c3df378e933205
|
|
BLAKE2b-256 checksum How to use checksums |
69cc36045f6f054d53f1a44acf3799680feb4d9175f32dd0966ec594a794ec03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for git-release-tagger 0.0.2
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.