Page MenuHomePhabricator

Investigate switching to the matterbridge-org/matterbridge fork
Open, Needs TriagePublicSpike

Description

https://github.com/matterbridge-org/matterbridge is a friendly fork of https://github.com/42wim/matterbridge that started because 42wim seems to have gotten busy with other things.

The current deployment of bridgebot is using https://gitlab.wikimedia.org/toolforge-repos/bridgebot-matterbridge/-/tree/work/bd808/T305487 as the core upstream. The patch that is applied there has been merged in both upstreams, but is not included in a tagged release by either. The matterbridge-org/matterbridge fork has not tagged anything yet; they do seem to be planning a release however.

Event Timeline

bd808 changed the subtype of this task from "Task" to "Spike".Thu, Jan 22, 10:20 PM

I think the thing to try here would be a branch of https://gitlab.wikimedia.org/toolforge-repos/bridgebot that pulls in a treeish from https://github.com/matterbridge-org/matterbridge instead of the one currently being used from https://gitlab.wikimedia.org/toolforge-repos/bridgebot-matterbridge.

I guess the way to test this would be to deploy the new build, test it in the matrix-telegram-test gateway, and be ready to quickly restore the previous image if it doesn’t work out? (Or use #wikimedia-cloud and let the people in there just deal with the test messages.)

I guess the way to test this would be to deploy the new build, test it in the matrix-telegram-test gateway, and be ready to quickly restore the previous image if it doesn’t work out? (Or use #wikimedia-cloud and let the people in there just deal with the test messages.)

https://gitlab.wikimedia.org/toolforge-repos/bridgebot/-/blob/main/etc/testing.toml and the testbot entrypoint are for testing things like this too. If I do this work I will probably build a new image using the alternate upstream, do some basic smoke tests with testbot to ensure that irc<->telegram bridging works in the testing channels, and then deploy the new container for the main bot.