debian-forge-composer

History

Tom Gundersen 4f39a33d34 osbuild-composer-koji.socket: use standard https port Rather than using the arbitrary port 8701, use the standard 443. The worker API will remain on a separate port, and as long as the two APIs are exposed by the same binary that will have to remain separate at 8700. Move the test instance of koji on localhost from 443 to 4343, to avoid a conflict. In a follow-up we should also give this API a prefix, so the cloud API can share the same port with it. Signed-off-by: Tom Gundersen <teg@jklm.no>		2020-09-17 17:34:57 +02:00
..
koji.go	upload/koji: don't pass task_id to cg_init_build	2020-09-16 00:15:02 +01:00
koji_test.go	osbuild-composer-koji.socket: use standard https port	2020-09-17 17:34:57 +02:00
README.md	upload/koji: reorganize run-koji-container script	2020-08-27 17:29:57 +01:00
run-koji-container.sh	osbuild-composer-koji.socket: use standard https port	2020-09-17 17:34:57 +02:00

How to run the Koji test

Firstly, you need to start the koji container:

sudo ./internal/upload/koji/run-koji-container.sh start

This command starts a kojihub instance available at http://localhost:8080/kojihub . You can test that it started successfully by running:

koji --server=http://localhost:8080/kojihub --user=osbuild --password=osbuildpass --authtype=password hello

Now, you can run the koji test using:

go test -v -tags koji_test ./internal/upload/koji

The test is run on each PR in the Github CI. See .github/workflows/tests.yml for more details.

To stop and remove the koji container, use the following command:

sudo ./internal/upload/koji/run-koji-container.sh stop