Learn more about these different git repos.
Other Git URLs
Regular RPM builds have an extra field of the build, relating to source and custom_user_metadata, while wrapperRPM build types don't.
extra
source
custom_user_metadata
From inspecting some builds and associated tasks, it appears that those extra fields get populated at build time for RPM builds, but not so for wrapperRPM builds. This might be wrong, but it appears so as wrapperRPM don't seem to have been considered when the container-ready-signing feature was implemented.
PR #3417
Metadata Update from @tkopecek: - Custom field Size adjusted to None
Metadata Update from @tkopecek: - Issue set to the milestone: 1.30 (was: 1.31)
Metadata Update from @tkopecek: - Issue set to the milestone: 1.31 (was: 1.30)
I see this issue has been updated to also ask for custom_user_metadata. I'm a little uncertain how we want custom-user-metadata to work outside the fairly narrow scope where it was first introduced. It is probably best to make that a separate discussion.
Metadata Update from @tkopecek: - Issue tagged with: testing-ready
Metadata Update from @jobrauer: - Issue tagged with: testing-done
Commit 8123106 fixes this issue
Commit 9ad7934 relates to this ticket
Login to comment on this ticket.