3480fe3093
From Koji Content Generator Metadata[1]:
"maven, win, or image: Legacy build type names which appear at this level
instead of inside typeinfo."
=> see, it's legacy
"typeinfo: A map whose entries are the names of the build types used for
this build, which are free form maps containing type-specific information
for this build."
=> struct{} is used for typeinfo.image because the docs says it should contain
"a free form map", null apparently isn't an option.
[1]: https://docs.pagure.org/koji/content_generator_metadata/
As suggested by the Brew maintainers Tomáš Kopeček and Lubomír Sedlář.
|
||
|---|---|---|
| .. | ||
| koji.go | ||
| koji_test.go | ||
| README.md | ||
| xmlrpc-response-oldapi.go | ||
| xmlrpc-response.go | ||
How to run the Koji test
Firstly, you need to start the koji container:
sudo ./tools/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 ./tools/koji/run-koji-container.sh stop