On Mon, Mar 19, 2018 at 8:08 PM, Jan Kaluza <jkal...@redhat.com> wrote:
> Your tool can use good old buildsys.build.state.change fedmsg with the > well known name/version/release fields like this: > > https://apps.stg.fedoraproject.org/datagrepper/ > raw?topic=org.fedoraproject.stg.buildsys.build.state.change > Initially I was very concerned about the idea of having to query Koji for each module to get NSVC, because in Taskotron we run ten thousand tasks per day and every unnecessary network request means slower execution, higher risk of failure and more logs to debug. We try to minimize the number of network requests as much as we can. However, if the structured metadata is/will be available in fedmsgs, I think I don't have a use case at hand that I could use to object to this. I still think it's a bad idea, though, and will bite us in the long run. > > That's staging, because it's easier for me to find the module builds there > :). > > Unfortunatelly, Koji does not add "type" field there, so you cannot find > out if that's module or not. > Is that something that will get resolved soon? Because it seems like a big blocker to any automated processing. If we want to run some tasks just on rpms and some tasks just on modules, how do we distinguish that?
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
