Container Workflow Tool
A python3 tool to make rebuilding container images easier by automating several steps of the process.
Motivation
The actual rebuild of container images consists of several steps that have been so far done manually. Some of these steps are:
- Rebase against upstream repository
- Check the changes made by the rebase
- Push the changes into dist-git and run the build
All of the steps are currently automated or semi-automated by cwt (but still need to be manually started). This should help a bit with the image rebuild workflow.
Requirements
- python3
- python3-GitPython
- python3-requests-kerberos
- fedpkg
Options
usage: cwt [options] command
Command:
koji - List builds, base images, hash ids
build - Command for building images
git - Work with upstream/downstream git repositories
utils - Other actions tied to the rebuild (communication, repository preparation etc.)
Options:
-v, --verbosity - Verbosity level, 1 (Critical only) - 5 (Debug messages), default 4 (Info)
--base - Specific base image release, required for some actions
--clear-cache - Clears tmp dir before running the command
--latest-release - Work with latest brew builds by release value
--config - Overrides default configuration file, expects the name of file a inside the config folder, optionally takes image_set argument
example usage: --config default.yaml:fedora27
--do-image - Use a custom set of images instead of all from the config (use dist-git names)
--exclude-image - Exclude an image from the list of images defined by config (use dist-git names)
--do-set - Use a specific set of images instead of all from the config (use dist-git names)
--tmp - Overrides default temporary working directory
--disable-klist - Disables getting kerberos token by klist
To get the usage of a specific command, you can run:
cwt command --help
container-workflow-tool in the quay.io registry
container-workflow-tool is automatically built and pushed in
quay.io/rhscl/cwt-generator as soon as changes
are merged into master branch.
Test
This repository also contains test suites for python's unittest framework that check the basic functionality of cwt.
These test can be run directly from the repository's root via Makefile:
make test
If you do not need to run all of the test cases provided you can run a module-specific subset like this:
make test_distgit
If you want to run all the test cases in container, run it like this:
make test-in-container
Metadata
Release files for container-workflow-tool 1.5.11
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 |
|---|---|---|---|---|
| container_workflow_tool-1.5.11.tar.gz | 34.3 kB | Without provenance | Details for container_workflow_tool-1.5.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| container_workflow_tool-1.5.11-py3-none-any.whl | Python 3 | none | any | Details for container_workflow_tool-1.5.11-py3-none-any.whl |
Total release size: 78.4 kB
Release files / container_workflow_tool-1.5.11.tar.gz
| Download URL | container_workflow_tool-1.5.11.tar.gz |
|---|---|
| Size | 34.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0279b80f63f04dddb2e187694fc893aa4bb130986cda7c5fc540e11d01b0178f
|
|
BLAKE2b-256 checksum How to use checksums |
6b7e13bbe761322a28f3e9a7d7c483ef4cea6c97e81e2d753a0b8e096eae83a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Release files / container_workflow_tool-1.5.11-py3-none-any.whl
| Download URL | container_workflow_tool-1.5.11-py3-none-any.whl |
|---|---|
| Size | 44.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
df7872b3e3f4d608515ffaf273f565ca8bd1a74d1aa8c25427a8ad317f3784aa
|
|
BLAKE2b-256 checksum How to use checksums |
22ca325617c57a15effbdf7aea051ab97444a6fc24a0c1ca5274002be3dcaae6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Security for container-workflow-tool 1.5.11
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.