On Mon, 2016-11-28 at 09:40 -0800, Adam Williamson wrote: > The validator/submitter component would be responsible for watching out > for new composes and keeping track of tests and 'test environments' (if > we keep that concept); it would have an API with endpoints you could > query for this kind of information in order to construct a result > submission, and for submitting results in some kind of defined form. On > receiving a result it would validate it according to some schemas that > admins of the system could configure (to ensure the report is for a > known compose, image, test and test environment, and do some checking > of stuff like the result status, user who submitted the result, comment > content, stuff like that). Then it'd forward the result to resultsdb.
It occurs to me that it's possible resultsdb might be designed to do all this already, or it might make sense to amend resultsdb to do all or some of it; if that's the case, resultsdb folks, please do jump in and suggest it :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
