dc4ae989e6
These tools were usually introduced when we added new upload target implementation to osbuild-composer. Their main purpose was manual testing of the upload library. They don't have any real use beyond that. With the upload code being moved to `osbuild/images` and these tools having their duplicates in that repository, there is very little sense in keeping them in osbuild-composer. Signed-off-by: Tomáš Hozza <thozza@redhat.com>
28 lines
819 B
Text
28 lines
819 B
Text
Binaries
|
|
========
|
|
|
|
osbuild-composer: The main binary, the service that maintains the queue and schedules all
|
|
jobs. This is started as the main process by systemd or container runtime.
|
|
|
|
osbuild-worker: The worker binary that handles jobs from the job queue locally.
|
|
|
|
osbuild-worker-executor: The binary that runs osbuild to build an image on an isolated VM.
|
|
|
|
Service binaries
|
|
================
|
|
|
|
osbuild-service-maintenance: Vacuum the database and remove old jobs. Also used to cleanup
|
|
cloud instances.
|
|
|
|
Development and test tools
|
|
==========================
|
|
|
|
mock-dnf-json
|
|
osbuild-auth-tests
|
|
osbuild-composer-cli-tests
|
|
osbuild-composer-dbjobqueue-tests
|
|
osbuild-dnf-json-tests
|
|
osbuild-koji-tests
|
|
osbuild-mock-openid-provider
|
|
|
|
osbuild-store-dump: the output from this is used in Test_upgrade in internal/store/json_test.go
|