Migrate 'coreos/fedora-coreos-tracker' to 'Webhook To Fedora Messaging' #1826
Comments
travier
added
meeting
|
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). |
|
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? |
|
@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. |
but isn't this what is behind the glue for sync2jira syncing? |
Yeah, I think you're right. Probably worth reaching out to them to see whether they're expecting individual repo owners to put in requests, or if they'll do a bulk request for everyone in there. Or maybe @gridhead knows. |
|
@jlebon Bundle em up in one ticket if you wish to move the entire namespace over to W2FM. |
|
@gridhead Have you reached out to the developers of Sync2Jira? https://github.com/release-engineering/Sync2Jira |
Basically a lot of consumers of github2fedmsg are probably using it explicitly for syncing issues into Jira via sync2jira. Those users won't be able to migrate until sync2jira supports it. We are wondering if you've discussed them with that team. |
|
I see that @ralphbean has made a bulk request against the migration issue tracker and I see that https://github.com/coreos/fedora-coreos-tracker/ is one of them. While we can take care of adding the entries but please note that the webhooks need to be set up by whoever has access to the repositories. As for now, no action is required at your end but we will let you folks know once we are done with the addition and that can be followed up by us notifying you about setting up the webhooks. @abompard I am referencing the issue ticket https://pagure.io/fedora-infra/w2fm-migration/issue/6 here. Is there anything else needed at the moment? |
That request is private I assume? |
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.
The text was updated successfully, but these errors were encountered: