Tox plugin that pushes status reports back to BitBucket.
Installation:
$ pip install hg+https://bitbucket.org/hpk42/tox@hook/report-status#egg=tox $ pip install tox-bitbucket-status
(You need to install the custom tox version for now, until the next version of tox is released).
Usage:
You need to ensure the following environment variables are set in your environment:
CI CI_NAME CI_COMMIT_ID CI_BUILD_URL BB_USERNAME (will default to $BB_REPO_OWNER if not set) BB_PASSWORD BB_REPO_OWNER BB_REPO_SLUG
Then, your commits will get a build status after they are pushed to BitBucket.
Just like the ones in this repository.
Codeship
The CI_* variables are all set by Codeship, but you will need to seth the BB_* variables yourself.
Jenkins
If you are using Jenkins and the Mercurial plugin, then some of the environment will be detected from the environment variables that are set:
CI → True CI_NAME → 'Jenkins' CI_BUILD_URL → $BUILD_URL CI_COMMIT_ID → $MERCURIAL_REVISION BB_REPO_OWNER : extracted from $MERCURIAL_REPOSITORY_URL BB_REPO_SLUG : extracted from $MERCURIAL_REPOSITORY_URL
At this point, the extraction of the owner/slug from the repo url only does sanity checking for mercurial repos (ie, that they are from bitbucket). Pull requests to support git repo urls will be accepted.
1 maintainer
Metadata
1 maintainer
Release files for tox-bitbucket-status 1.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 |
|---|---|---|---|---|
| tox-bitbucket-status-1.0.tar.gz | 2.8 kB | Without provenance | Details for tox-bitbucket-status-1.0.tar.gz |
Release files / tox-bitbucket-status-1.0.tar.gz
| Download URL | tox-bitbucket-status-1.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3713ebb05a5c0ff963fd39997e87769de19e54f33f160ac95c807b9aa2147ac
|
|
BLAKE2b-256 checksum How to use checksums |
726e1dcc44bba038e97c30174c9466133685f692f48799bb4c2ceaa2e6db0145
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tox-bitbucket-status 1.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.
