Simple way to release past(or current) commits within Jira
Credit to @shamrin for the name generator code [https://github.com/shamrin/namesgenerator](https://github.com/shamrin/namesgenerator)
```
usage: ci-jira-releaser [-h] -p PROJECT_KEY -u JIRA_URL [-r REPO_ROOT]
[-U JIRA_USERNAME] [-P JIRA_PASSWORD] --from-commit
FROM_COMMIT [--to-commit TO_COMMIT]
[--project-name PROJECT_NAME]
[--build-number BUILD_NUMBER] [--development]
[--production]
A simple way to label development tags or auto make a releaser within Jira
optional arguments:
-h, --help show this help message and exit
-p PROJECT_KEY, --project-key PROJECT_KEY
The Jira project key: e.g PROJ
-u JIRA_URL, --jira-url JIRA_URL
The url Jira is located at including http://
-r REPO_ROOT, --repo-root REPO_ROOT
The location of the git repo, must have a .git inside
-U JIRA_USERNAME, --jira-username JIRA_USERNAME
environment_var[JIRA_USER]
-P JIRA_PASSWORD, --jira-password JIRA_PASSWORD
environment_var[JIRA_PASSWORD]
--from-commit FROM_COMMIT
Hash of git commit to start grabbing issues from
--to-commit TO_COMMIT
End commit to parse through
--project-name PROJECT_NAME
The name of the project to help generate the label
--build-number BUILD_NUMBER
For build systems usually an environment variable.
Usually passed by Jenkins as a ENV variable.
--development Pass flag if using for development
--production Pass flag if using for production
Don't forget you can use environment variables
```
Examples
--
Development
---
```
ci-jira-releaser -p PROJ -u http://site.atlassian.net --from-commit SHA -r ~/my-project --project-name my-project --build-number 123 --development
```
Production
---
```
ci-jira-releaser -p PROJ -u http://site.atlassian.net --from-commit SHA -r ~/my-project --production
```
1 maintainer
Metadata
1 maintainer
Release files for ci-jira-releaser 0.3.8.7
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 | |
|---|---|---|---|---|
| ci-jira-releaser-0.3.8.7.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ci_jira_releaser-0.3.8.7-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 9.7 kB
Release files / ci-jira-releaser-0.3.8.7.tar.gz
| Download URL | ci-jira-releaser-0.3.8.7.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf0a7b4fb19fa19ac79a2b443a580426c6ccd5bf822f37492c7765a4116bc0e9
|
|
BLAKE2b-256 checksum How to use checksums |
654aae92c9dd20243929402c844215dc253412315edce237c8e5e9605fe7e1d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / ci_jira_releaser-0.3.8.7-py2-none-any.whl
| Download URL | ci_jira_releaser-0.3.8.7-py2-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
cbc1463dd99a3740a965760e0f9e1c7a6506834e6e41c228a2f6ad766eda76fc
|
|
BLAKE2b-256 checksum How to use checksums |
c9e8c3512739d2f6158c50c6069438445a6e6f3aa3a22a74817065cf8dc21455
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ci-jira-releaser 0.3.8.7
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.
