debian-forge-composer/internal/upload/koji
Tom Gundersen e52830f530 upload/koji: don't pass task_id to cg_init_build
Contrary to our assumption, we cannot initialize the build with the
link to the task. We can only update the link once the build has
completed.

This seems like a bug in koji, but we keep it like this for now.
2020-09-16 00:15:02 +01: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 upload/koji: don't pass task_id to cg_init_build 2020-09-16 00:15:02 +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: add support for GSSAPI/Kerberos auth 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