debian-forge-composer/internal/upload/koji
Ondřej Budai bc02da786d upload/koji: ensure that Koji type instance is always logged-in
Previously, Koji instance could be both logged-in and not logged-in.
This change disallows it: Now, the Koji instance is created by calling
koji.Login, so it must be always logged-in. This change should lead to more
robust code.
2020-08-27 17:29:57 +01:00
..
koji.go upload/koji: ensure that Koji type instance is always logged-in 2020-08-27 17:29:57 +01:00
koji_test.go upload/koji: ensure that Koji type instance is always logged-in 2020-08-27 17:29:57 +01:00
README.md upload/koji: reorganize run-koji-container script 2020-08-27 17:29:57 +01:00
run-koji-container.sh upload/koji: reorganize run-koji-container script 2020-08-27 17:29:57 +01: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