Add fedmsg listener to openqa tools
AbandonedPublic

Authored by adamwill on Feb 23 2016, 10:05 AM.

Details

Summary

As pungi4 is about to be rolled live, we need a quick fedmsg listener/consumer to kick off fedmsg jobs. This is as per irc conversation with adamw.

Test Plan

use fedmsg-dg-replay to replay the following fedmsg:

https://apps.fedoraproject.org/datagrepper/id?id=2016-85af2c7b-be8d-4225-a238-3ca3bd2e2d5c&is_raw=true&size=extra-large

Note that this should /not/ trigger any jobs. Finding a finished pungi compose fedmsg seems to be a bit problematic; it appears many composes "failed in a horrible fire" or are "FINISHED_INCOMPLETE"

Diff Detail

Repository
rOPENQA fedora_openqa
Lint
Lint Skipped
Unit
Unit Tests Skipped
jdulaney retitled this revision from to Add fedmsg listener to openqa tools.Feb 23 2016, 10:05 AM
jdulaney updated this object.
jdulaney edited the test plan for this revision. (Show Details)
jdulaney added a reviewer: adamwill.
jdulaney set the repository for this revision to rOPENQA fedora_openqa.
jdulaney added a project: fedora_openqa.
jdulaney added subscribers: jdulaney, kparal.

Sidenote: all finished Pungi 4 composes have "FINISHED_INCOMPLETE" in "status" (see here, all are either DOOMED or FINISHED_INCOMPLETE). Don't know why. Maybe it indicates that it was finished, but not everything was built (e. g. ARM disk images that aren't there)?

garretraziel requested changes to this revision.Feb 23 2016, 12:09 PM
garretraziel added a reviewer: garretraziel.

According to this, we should listen also for "FINISHED_INCOMPLETE" status change.

This revision now requires changes to proceed.Feb 23 2016, 12:09 PM
kparal removed a subscriber: kparal.Feb 23 2016, 3:20 PM
adamwill added a comment.EditedFeb 23 2016, 3:27 PM

Yes, I'd say just do if 'FINISHED' in status: for now. Other than that this looks fine for now. Wiki reporting is probably going to need to be rethought, but let's do one step at a time.

Actually, thinking about it a bit harder, I think maybe drop the wiki report attempt for now. It will block the listener until all jobs are complete, which takes some time. I'd rather not do that, so that when we're getting multiple composes in a fairly short space of time (e.g. Branched and Rawhide) we aren't waiting for the jobs from one to complete before running the other.

I'll be thinking through how to make wiki reporting happen properly when we get to that.

adamwill requested changes to this revision.Feb 23 2016, 3:28 PM
jdulaney updated this revision to Diff 1934.Feb 23 2016, 6:49 PM

I think it may not be a bad idea to log the fact that jobs are run in some form, so I switched to doing that instead of reporting to the wiki.

adamwill accepted this revision.Feb 23 2016, 8:47 PM

I merged this manually to the pungi4 branch with a couple of trivial changes, since we don't want this stuff on develop yet, we want to review all the pungi4 together as one big diff when it's ready. Thanks John!

adamwill commandeered this revision.Feb 23 2016, 8:47 PM
adamwill abandoned this revision.
adamwill edited reviewers, added: jdulaney; removed: adamwill.