# openqa_review_script [](https://travis-ci.com/os-autoinst/openqa_review) [](https://bestpractices.coreinfrastructure.org/projects/699)
A review helper script for openQA.
For more details read the documentation within openqa_review/openqa_review.py.
## Usage
Install requirements and package, using an isolated Python environment such as [VirtualEnv](http://docs.python-guide.org/en/latest/dev/virtualenvs/).
` pip3 install -r requirements.txt pip3 install . `
or if you are using openSUSE distribution, it is recommended to use zypper, e.g.:
` zypper in python-openqa_review `
Call openqa-review from PATH, e.g. with –help
` openqa-review --help `
If openqa-review has to access non public servers which make use of custom Certificate Authorities (CA’s), it can happen that it fails because it can not verify the TLS certificate. By setting the environment variable REQUESTS_CA_BUNDLE, one can supply a custom ca-certificate store to openqa-review e.g.:
` REQUESTS_CA_BUNDLE="/my/custom/ca-bundle.pem" openqa-review `
If that doesn’t work, you can try the following setting: ` CURL_CA_BUNDLE="" `
## Communication
If you have questions, visit me on irc.freenode.net in #opensuse-factory
## Contribute
This project lives in https://github.com/os-autoinst/openqa_review
Feel free to add issues in github or send pull requests.
TODOs and ideas are tracked in the file TODO as well as github issues.
### Rules for commits
Every commit is checked by [Travis CI](https://travis-ci.com) as soon as you create a pull request but you should run tox locally,
Make sure to keep the 100% test coverage, e.g. by adding test reference data for new scenarios. TDD is advised :-)
For git commit messages use the rules stated on [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/) as a reference
If this is too much hassle for you feel free to provide incomplete pull requests for consideration or create an issue with a code change proposal.
## License
This project is licensed under the MIT license, see LICENSE file for details. Exceptions are the files under dashboard_files/ which are GPL-2 licensed coming from https://github.com/os-autoinst/openQA/.
1 maintainer
Metadata
1 maintainer
Release files for openqa-review 1.25.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 | |
|---|---|---|---|---|
| openqa_review-1.25.0.tar.gz | 40.2 kB | Without provenance | Details |
Release files / openqa_review-1.25.0.tar.gz
| Download URL | openqa_review-1.25.0.tar.gz |
|---|---|
| Size | 40.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4efe98dfabaab12fe6f8f49b7734313d392f5e78ff03aadd73c9c31fd6743e62
|
|
BLAKE2b-256 checksum How to use checksums |
06c00a4724b4568e7ba883efa867bd2d3a1eeb057f1672015aff89f5c26a9e19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.8.7
|
Security for openqa-review 1.25.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.
](https://travis-ci.com/os-autoinst/openqa_review){kind=link}