When a new version of the package is pushed as a follow-up of an issue, it seems that the maintainer needs to manually close the task. See https://pagure.io/centos-sig-hyperscale/package-updates/issue/11 where I left the task opened to see if the tooling would eventually close it. It would be convenient if the tooling could autodetect the update and close the task. This will avoid dangling task in the future. It could also automate messaging with what package version is solving the issue as well as commit if possible.
The fedora messaging looks good for this: https://fedora-messaging.readthedocs.io/en/stable/
Listen on these two topics to autodetect cbs builds could help to solve the auto-close: - org.centos.prod.cbs.buildsys.build.state.change - org.centos.prod.cbs.buildsys.tag
The payloads have the package version and commit.
I think we can have running this logic in a separated instance, one listening on MQTT (the one that is already running) and the other on AMQP (for this one).
Metadata Update from @chantra: - Issue tagged with: package-updater
Done https://pagure.io/centos-sig-hyperscale/package-updates/issue/34 https://pagure.io/centos-sig-hyperscale/package-updates/pull-request/29
Metadata Update from @oidoming: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.