koji

#3110 RFE: expose build.extra by listTagged API directly
Closed: Fixed by tkopecek. Opened by julian8628.

Closed: Fixed
Reopen Issue

The extra info of the CG-imported builds (module, osbs, etc) might contain useful information for users and other integrated ends. Now, they are using listTagged with getBuild to query the data. Adding build.extra would save much client effort for the client to grep this data.

I want to get the Extra info of all builds (in particular: module info info extra.typeinfo.module, extra.typeinfo.remote-sources, extra.external_build_id, extra.osbs_build, extra.image, extra.build_system) that are part of a tag.

Right now I do listTagged to retrieve the build IDs and then perform a getBuild for each ID to retrieve the additional extra details I need. There are X workers performing the requests in parallel, but still this seems a bottleneck as you have to perform an extra operation just to get very few additional details that are not provided by listTagged.

What is the broader issue with modules that you're trying to solve, @ret2libc ?

PR 3282

Metadata Update from @jcupova:
- Custom field Size adjusted to None

Metadata Update from @jcupova:
- Issue set to the milestone: 1.29

Metadata Update from @tkopecek:
- Issue tagged with: testing-ready

Metadata Update from @tkopecek:
- Issue untagged with: testing-ready

Metadata Update from @jcupova:
- Issue tagged with: testing-ready

Metadata Update from @mfilip:
- Issue tagged with: testing-done

Commit 87aa8eb1 fixes this issue

Commit 75d545e7 fixes this issue

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/3110

Please continue any further discussion there.
Metadata
None

testing-done testing-ready usability wishful

None
None
Low
None
Related Pull Requests
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.