#851 RFE: store optional build label for CG builds
Closed: Dropped 2 years ago by tkopecek. Opened 6 years ago by dgregor.

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/66LGXM26UVRHR76CXGMR33MDEFJ6XFHW/

When builds are imported into the Koji using the content generator interface they must provide name, version and release values to identify the builds. Koji uses n-v-r as a unique identifier for all builds regardless of build type. However, some build types are not natively represented in a n-v-r fashion.

The particular example in this case is modules. They use NAME:STREAM:VERSION:CONTEXT for identification. Having these builds displayed and referenced by n-v-r causes confusion. See the linked email thread for context.

I suggest that the CG metadata format be extended to allow for an optional "identifier" field in the "build/extra" section. This would be a string. This string would be queryable through the koji API. Also, when present, this would be used in the web ui instead of n-v-r. Example:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1055963


Metadata Update from @mikem:
- Issue tagged with: discussion

6 years ago

Dropping, should be part of MBS integration work.

Metadata Update from @tkopecek:
- Custom field Size adjusted to None
- Issue close_status updated to: Dropped
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata