scheduler: add a result reporting fedmsg consumer
ClosedPublic

Authored by adamwill on Mar 18 2016, 2:20 AM.

Details

Summary

actually three of them - prod, stg and test variants. These
should listen for openQA 'job complete' fedmsgs and report
results to the wiki. The prod consumer listens for prod fedmsgs
and reports to the prod wiki, the stg consumer listens for
stg fedmsgs and reports to the stg wiki, the test consumer
listens for dev fedmsgs and doesn't report anywhere, it just
logs the ResTups.

Tweaked the result reporting functions in report.py a little
bit so they return the ResTups if do_report is False, to allow
the logging.

Test Plan

Enable the test consumer, throw a fedmsg-dg-replay
at it, and see if it works right. I recommend msg id
2016-fa43f1e9-9c6f-40c7-ae4c-f916d9386792 - that's a passed
test. Make sure your openQA client.conf points at the same
openQA server that produced the fedmsg you test with!

You could hack up the consumers a bit to test actual wiki
reporting too, just be careful.

Diff Detail

Repository
rOPENQA fedora_openqa
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
adamwill retitled this revision from to scheduler: add a result reporting fedmsg consumer.Mar 18 2016, 2:20 AM
adamwill updated this object.
adamwill edited the test plan for this revision. (Show Details)
adamwill added reviewers: jskladan, garretraziel.
garretraziel accepted this revision.Mar 21 2016, 3:04 PM

Looks OK, I guess...

This revision is now accepted and ready to land.Mar 21 2016, 3:04 PM
This revision was automatically updated to reflect the committed changes.