BODGER
The bodger tool is a very simple wrapper that reads a config, matches grainss, and determines what command to run, and runs it. This makes it easy to set what commands to run for test, build, docs etc in a CI/CD pipeline. You can kind of think of it like a platform specific Make command with a better config.
Config
The default config is “bodger.conf” and should be located inside of the root of a project.
This config looks like this:
bodger:
test:
kernel:Linux: pytest
pkg:
os:Arch: tiamat -c build.conf --pkg-tgt Arch
os_family:RedHat: tiamat -c build.conf --pkg-tgt rhel7
bin:
kernel:Linux: tiamat -c build.conf
Then the system can by run by calling bodger <cmd>:
bodger test bodger pkg bodger bin
Metadata
Release files for bodger 4.2.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 |
|---|---|---|---|---|
| bodger-4.2.0.tar.gz | 8.2 kB | Without provenance | Details for bodger-4.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bodger-4.2.0-py3-none-any.whl | Python 3 | none | any | Details for bodger-4.2.0-py3-none-any.whl |
Total release size: 16.9 kB
Release files / bodger-4.2.0.tar.gz
| Download URL | bodger-4.2.0.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1a15bcc3e08970fa8760ead64efd880b943dace3c517e86105126f4cfd9fd00
|
|
BLAKE2b-256 checksum How to use checksums |
8d87b155b8028d0ed2d30fde9107ee258fb18d7a736b8affe659242793d39ed2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.7
|
Release files / bodger-4.2.0-py3-none-any.whl
| Download URL | bodger-4.2.0-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d08a3eac18017bf595c5bd8659df3d8606c4561beba40f4725510b32cfb1874
|
|
BLAKE2b-256 checksum How to use checksums |
3c743cc46a5dbe4452315a2da6919984f86af98e01a2d068c8700ba929baea99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.7
|
Security for bodger 4.2.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.