> However, taskotron/resultsdb message do not include the koji
task it was
> running
> the tests against.
The code to process Koji scratch builds is very experimental and I don't know
if it's already deployed somewhere, but the published result should
definitely include Koji task ID. It should be even reported as the "item"
(and the type of the result is "koji_task"). Can you link to results which
fail to do that? I can look for bugs. (Provided we even reported such
results already, again, I'm not sure.)
I realized you didn't actually mention *scratch* builds in your message. In case
you're using standard Koji builds, then yes, that would be a problem. But I can't
imagine we would want to use standard Koji builds for this, right? That doesn't seem
right. And for scratch builds, the implementation should already exist as described above.
So if there's any reason why you wouldn't want to use scratch builds, please shout
and we can discuss. Otherwise we should be good to go here.