zoe_ci Job framework
If you are new to zoe_ci, look at the architecture docs there: misc/ZoeArch.md
This repository is the client part of the zoe_ci architecture that executes work items on target machines.
It consists of:
Conventions
- All jobs should be in files named
*.job.py. This way the version control systems can trigger jobs correctly. - Only one job per file
- Try to keep complexity down as much as possible, increasing maintainability of the overall system
- Try to write the code in a cross-platform matter if simple enough (linux/windows/console)
Installation
pip install zoe
to run:
python -m zoe_ci
Development: start / testing
Run the solution in vscode with F5, see .vscode/launch.json
Manual testing
just execute any .job.py file in python:
examples\\01-simple-svn-checkout.job.py
1 maintainer
Metadata
1 maintainer
Release files for zoe-ci 0.1.38
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 |
|---|---|---|---|---|
| zoe_ci-0.1.38.tar.gz | 19.3 kB | Without provenance | Details for zoe_ci-0.1.38.tar.gz |
Release files / zoe_ci-0.1.38.tar.gz
| Download URL | zoe_ci-0.1.38.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7eb143af5f940c1a03e05812247d73ce34aa92260be259d6ca0477a9d1613359
|
|
BLAKE2b-256 checksum How to use checksums |
faf06733c59173821a0e25b329d9709ad01d393dc978c50f157844e3c94ced82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Security for zoe-ci 0.1.38
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.
