fm-orchestrator

#416 Track the list of binary artifacts in the modulemd
Closed Opened by ralph.

Closed
Reopen Issue

Before the module reaches the "ready" state, the modulemd needs to be modified to include a list of binary artifacts -- the built rpms from the module build.

This is needed (eventually) for end client tooling which will look in a merged repo of many modules. It will need to know which binary artifacts come from which input modules.

A thought about how to do this:

  • When the module build enters the done state, it should publish an updated modulemd with the new binary rpm information.
  • pdc-updater should pick that up and update the existing entry in PDC.
  • Pungi will be querying pdc to get that information for the compose.

Metadata Update from @jkaluza:
- Issue assigned to jkaluza

Metadata Update from @jkaluza:
- Issue assigned to jkaluza

Metadata Update from @jkaluza:
- Assignee reset

So - will the binary modulemd contain rpms for all the architectures? That's how we do things for koji content generator ATM. But it means it doesn't really represent what will be in a arch-specific repo - is that a problem?
  • In composes, we are doing this.
  • In PDC, we do it also, but not in the modulemd. In a PDC field.

Metadata Update from @ralph:
- Issue status updated to: Closed (was: Open)

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

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.