#7879 Update fedmsg_meta in production
Opened 3 months ago by adamwill. Modified 14 days ago

The current production fedmsg_meta_fedora_infrastructure cannot cope with the current format of CI pipeline messages, meaning everyone who does package builds gets tons of "there was a problem making them human-readable" errors from the notification system.

I fixed this, but the fix has not yet been deployed to production. Can we please do whatever is necessary to make that happen? Thanks.

@puiterwijk @pingou


Metadata Update from @puiterwijk:
- Issue assigned to puiterwijk

3 months ago

@puiterwijk Are you still going to do this? Is there perhaps a SOP or readme one of the rest of us could follow to do a upstream release and update?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

3 months ago

Note I still have a PR outstanding that significantly improves Bugzilla message handling:

https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/497

and I'm working on another for Bodhi. It's kinda painful that it's so hard to get improvements to this actually rolled out.

I've release 0.28.0.
It's built in f30, f29 and epel7 (failed to build in rawhide, I'll need to check this, it's likely related to the deprecation of python2).

Thanks, it'd be great if this could finally get done...

I've release 0.28.0.
It's built in f30, f29 and epel7 (failed to build in rawhide, I'll need to check this, it's likely related to the deprecation of python2).

Did you push bodhi updates too? Or just built into infra-tags? I don't see it...

I sent some improvements for openQA messages last week, so maybe if we could get 0.29.0 too...

@pingou I guess you built but didn't push updates?

Can you build 0.29.0 and push updates and we can update it after freeze?

Metadata Update from @kevin:
- Issue assigned to pingou (was: puiterwijk)
- Issue tagged with: unfreeze

17 days ago

I'll do 0.29.0 right now :)

Login to comment on this ticket.

Metadata