cico
deploy CI results to git
cico commits artefacts generated by a CI enviroinment to a Git results branch.
For each tested branch a directory in the results branch gets created.
- tested branch: The branch you commited an is checked out by the CI tool
- results branch: The branch where your results should be deployed
- can be in a different repository than the tested branch
Installation
$ pip install cico
Usage
deploy.py
from cico import TravisCI
from cico.results import Directory, File, Badge
TravisCI(
repo = GitHub(USERNAME, # GitHub Username (e.g. 'stefanhoelzl')
REPO_NAME, # GitHub Repository (e.g. 'ci-results')
TOKEN), # GitHub Personal access tokens
# ONLY ENCRYPTED (https://docs.travis-ci.com/user/environment-variables/#Defining-encrypted-variables-in-.travis.yml)
branch = RESULT_BRANCH, # Git Branch with the results (e.g. 'cico-testing')
results = [
# Deploy file 'testresults.tap' into folder 'tap' (destination is optional)
File("testresults.tap", destination="tap"),
# Deploy file 'wrong_name.tap' as 'correct_name.tap' (rename is optional)
File("wrong_name.txt", rename="correct_name.txt"),
# Deploy directory 'covhtml' into folder 'coverage' (desitnation is optional)
Directory("covhtml", destination="coverage"),
# Create a Badge with the label "My Badge" and value "96" as mybadge.svg and mybadge.png
# (png is optional) in the directory 'badges'
Badge("badges/mybadge", png=True, label="My Badge", value=96,
**anybadge_arguments), # https://github.com/jongracecox/anybadge
]
).commit(
# commit message (optional)
# {build} gets replaced by build number
# {branch} gets replaced by name of tested branch
message="build {build} on branch {branch}",
# perform 'git push' even if not executed in CI environment (default=False)
no_ci_push=True
)
.travis.yml with after_script section
after_script:
- python deploy.py
.travis.yml with deploy section
deploy:
provider: script
skip_cleanup: true # prevent TravisCI from cleaning up the files you want to deploy
script: python deploy.py
directory structure afterwards in branch cico-testing of the repository ci-results
+-- master
o-- correct_name.txt
+-- tap
| o-- testresults.tap
+-- covhtml
| +-- <all contents of covhtml in the tested branch>
+-- badges
o-- mybadge.svg
o-- mybadge.png
Metadata
Release files for cico 0.1.8
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 |
|---|---|---|---|---|
| cico-0.1.8.tar.gz | 4.4 kB | Without provenance | Details for cico-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cico-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for cico-0.1.8-py3-none-any.whl |
Total release size: 10.1 kB
Release files / cico-0.1.8.tar.gz
| Download URL | cico-0.1.8.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
600e9be449f405d788a232bc4f6699b841c4478e1dd75a5c16ebb0618a30c1d8
|
|
BLAKE2b-256 checksum How to use checksums |
62008b46b03b86fe4762fa7f9b2b813b6df80a6bc38484ddbf93ad6b51adc3ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / cico-0.1.8-py3-none-any.whl
| Download URL | cico-0.1.8-py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4b1106175735feca1c21f6315089544a0f28438a9f79be64b233125a7cfda16b
|
|
BLAKE2b-256 checksum How to use checksums |
ae840c52ba369babdb085ee003b5c817eecd5c5d7c5945aea692dea060146c3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cico 0.1.8
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.