Configuration
jirator will look in ~/.jirator/config for a configuration file, which will specify server to use, credentials for the server and what issue statuses jirator should consider as "open" issues (i.e. the ones that will be shown for you).
Example config
{
"server": "http://localhost:2990/jira",
"username": "fredsusername",
"password": "fredspassword",
"status": ["TO DO","IN PROGRESS","ON HOLD", "IN REVIEW", "OPEN"]
}
Contributing
Contributions are welcome. Note that all contributions are subject to the license of this project.
Setup up dev environment
- Install the atlassian-plugin-sdk to get a local instance of the Jira REST API to test against. Follow the instructions at
- https://developer.atlassian.com/server/framework/atlassian-sdk/downloads/
- https://developer.atlassian.com/server/framework/atlassian-sdk/create-a-helloworld-plugin-project/
- Run Jira by being in the plugin directory and running
atlas-run - When you've created your plugin and the server is running, login and create a project and a few issues to test on
Create a release
Run the following command in the root path:
python setup.py sdist
install locally:
pip install (--user) /path/to/tarfile
Metadata
Release files for jirator 0.1.4
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 |
|---|---|---|---|---|
| jirator-0.1.4.tar.gz | 4.5 kB | Without provenance | Details for jirator-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jirator-0.1.4-py2-none-any.whl | Python 2 | none | any | Details for jirator-0.1.4-py2-none-any.whl |
Total release size: 10.8 kB
Release files / jirator-0.1.4.tar.gz
| Download URL | jirator-0.1.4.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bb660dd8c936a493e2da8898220e3ef89142127dd04802cfac0cc5199af5abb9
|
|
BLAKE2b-256 checksum How to use checksums |
7a3ad6e2869b0f93151b43accc0463759d30bed592a764e1f3c56df0bb2f890a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.4 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.13
|
Release files / jirator-0.1.4-py2-none-any.whl
| Download URL | jirator-0.1.4-py2-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
abdec951da637903e17862bc9fd66358787e3a5aea2d332e5c85444d522e8279
|
|
BLAKE2b-256 checksum How to use checksums |
383f4f7d3692796ad69da35e82408ddde8a5ceb83930ea8e6706a90762e95149
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.4 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.13
|
Security for jirator 0.1.4
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.