fm-orchestrator

#948 Let the metadata.json file include the rpmID for each rpm builds
Closed: Invalid Opened by chcao.

Closed: Invalid
Reopen Issue

Here in one module build, there is a metadata.json file, and we are using the metadata["output"]["components"] data, can you also add the brew's rpmID in each rpms?

The metadata is something like:
{...
"output": [
{
...
"components": [ {
"name": "XXX",
"sigmd5": "XXX",
"arch": "XXX",
"epoch": xx,
"version": "xx",
"release": "xxx",
"type": "xxx"
}, }
....

The rpmID is something like "/rpminfo?rpmID=12345678"

I don't think the RPM ID is meant to be in the metadata.json.
From Koji's Content Generator API doc:

components: List of maps containing information about content installed in the build environment (if any). Each map is guaranteed to contain a type field, which determines what other fields are present in the map. For maps where type = rpm, the following fields will be present:
name: The rpm name.
version: The rpm version.
release: The rpm release.
epoch: The rpm epoch.
arch: The rpm arch.
sigmd5: The SIGMD5 tag from the rpm header.
signature: The signature used to sign the rpm (if any).

https://docs.pagure.org/koji/content_generator_metadata/

Based on my previous comment, let's drop this.

Metadata Update from @lucarval:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

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

Please continue any further discussion there.
Metadata
None
None
None
None
None
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.