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.
Details
- Reviewers
garretraziel jdulaney
use fedmsg-dg-replay to replay the following fedmsg:
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
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)?
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.
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.
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!