On 01/02/2017 08:47 AM, Martin Krizek wrote: > Hi Jeremy, > > I am not aware of any obstacles. To enable this we only need to push a > change into Taskotron Trigger that would listen on the koji scratch > fedmsgs and then wire your task to it. We can start in our dev instance > and see how it goes from there. Let us know if you need any help > with the "the-new-hotness" task.
That sounds great. I had imagined that there wouldn't be a "the-new- hotness" specific task. I'm _really_ unfamiliar with this part of the Fedora infrastructure, so maybe it would be helpful for me to explain what I imagine to be true: From my understanding, a set of tests are run against real Koji builds. These test results are displayed in Bodhi ([0] for example). My scheme was to use this exact same set of tests, but also run them on scratch builds (or, perhaps, a subset of the tests). I'd then show them to the user. Am I making a false assumption in something above? Is there more to be done than adding the scratch build fedmsg topic to the same task that runs on real Koji builds? Thanks in advance for putting up with my ignorance :) [0] https://bodhi.fedoraproject.org/updates/FEDORA-2017-e7f9c23746 -- Jeremy Cline XMPP: jer...@jcline.org IRC: jcline
signature.asc
Description: OpenPGP digital signature
_______________________________________________ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
