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

Create Rococo <> Westend bridge relayer in polkadot-sdk #2952

Closed
serban300 opened this issue Apr 15, 2024 · 1 comment
Closed

Create Rococo <> Westend bridge relayer in polkadot-sdk #2952

serban300 opened this issue Apr 15, 2024 · 1 comment
Assignees

Comments

@serban300
Copy link
Collaborator

Related to #2950

Right now the CI tests that we have inside polkadot-sdk use the runtimes from polkadot-sdk, and the relayer release from parity-bridges-common. The problem with this approach is that when we make a change to the relayer, the CI doesn't actually test it on the spot. For this kind of changes we have to run the tests locally manually.

We should create a Rococo <> Westend relayer flavor inside polkadot-sdk in order to address this limitation. For convenience we can also keep the Rococo <> Westend flavor inside the parity-bridges-common.

@acatangiu
Copy link
Collaborator

I think maintaining parity-bridges-common "mirrored" code in polkadot-sdk is more cumbersome/expensive than having to sanity check relayer changes using local testing before publishing new version.

This would also make the R<>W relayer development&deployment process different than the P<>K relayer, which again adds more maintenance complexity.

Closing it. Please reopen if you strongly disagree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants