Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate 'coreos/fedora-coreos-tracker' to 'Webhook To Fedora Messaging' #1826

Open
gridhead opened this issue Nov 6, 2024 · 4 comments
Open
Labels
infra Related to Fedora Infrastructure team work/input meeting topics for meetings

Comments

@gridhead
Copy link

gridhead commented Nov 6, 2024

This project was listed in the GitHub2FedMsg database and we want to you to inform you about the upcoming deprecation of the service. As the Fedora Infrastructure is finishing up with migrating its applications away from FedMsg to Fedora Messaging, we encourage you to migrate your repository to the successor of the GitHub2FedMsg project, Webhook To Fedora Messaging.

Please follow this link to the official announcement of the project’s release and use the instructions there to migrate to the new service. If this notification was a mistake, please close this notification ticket. We will not act on the repositories whose migrations have not been requested and any related GitHub2FedMsg operations will stop working once the service is decommissioned.


@jlebon
Copy link
Member

jlebon commented Nov 6, 2024

I don't think we need to migrate any of those. We don't really need GitHub notifications on the bus for any of those repos.

The only repo we monitor on the bus AFAIK is https://github.com/coreos/fedora-coreos-config, so that coreos-koji-tagger knows when there are updated lockfiles to process. But that repo is presumably already migrated since it's not on the list (and coreos-koji-tagger definitely is using fedora-messaging).

@jlebon
Copy link
Member

jlebon commented Nov 6, 2024

Oh wait, I see you filed coreos/fedora-coreos-config#3242.

So basically we need to file an issue against https://pagure.io/fedora-infra/w2fm-migration/issues and that's it? Do consuming apps need to be adapted in any way or it'll just keep working exactly the same?

@gridhead
Copy link
Author

gridhead commented Nov 7, 2024

@jlebon yes, and we should take it from there. The consuming apps should be able to get messages from the Fedora Messaging bus so as long as they are listening to it, things should work the way they are.

@dustymabe
Copy link
Member

I don't think we need to migrate any of those. We don't really need GitHub notifications on the bus for any of those repos.

but isn't this what is behind the glue for sync2jira syncing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infra Related to Fedora Infrastructure team work/input meeting topics for meetings
Projects
None yet
Development

No branches or pull requests

4 participants