We're looking to start running rpminspect for all builds coming out of koji and make those results available for gating decisions. Given the restrictions of the current infrastructure that we're using to run all of this, we have no choice but to emit fedmsgs until more progress is made by other parties to support fedora-messaging.
As such, I'm requesting certs to emit fedmsgs for the results coming from rpminspect (for now, maybe more later) so that they can make it through the existing systems.
topic: org.centos.[prod/stg]ci.generic.*
This will be emitted by an openshift project in apps.ci.centos.org if that is important for the cert creation. Separate certs for stg and prod are fine if that makes things easier
ci.centos.org already has fedmsg and fedora-messaging certs. Would these be fine for you? If so I guess you need to sync up with @bstinson
If that can work, I'm fine with the idea. I was under the impression that we'd have to get that set up on our own since we're in a different project.
I'll sync up with him and see what I can find out
Do note also that we have 2 gateways that republish from fedmsg->fedora-messaging and vice versa. So, either bus should see the same messages. In which case, we should really prefer fedora-messaging if at all possible.
Metadata Update from @kevin: - Issue priority set to: Waiting on Reporter (was: Needs Review)
My hands are slightly tied here. As I understand it, the Jenkins plugin that handles messaging does not yet support fedora-messaging so until that happens, I don't think that fedora-messaging is an option.
I talked to @bstinson about this and have a method for emitting fedmsgs that works for now. It will need some changes once the other CI stuff migrates to fedora-messaging but I figure we'll cross that bridge when we get there.
Metadata Update from @tflink: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.