Skip to content

Switch to the new version of jacogr/polkadot-js-tools #1594

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

Merged
merged 6 commits into from
Jun 15, 2023

Conversation

wilwade
Copy link
Collaborator

@wilwade wilwade commented Jun 13, 2023

Goal

The goal of this PR is to upgrade the polkadotjs tools for metadata comparison.

Closes #1230

This also includes PR #1601 for expediency. So also part of #1362

Ended up needing to run each one in a docker container with a new docker network. This allowed everything to talk correctly.

Checklist

@wilwade wilwade force-pushed the chore/update-comp-metadata-docker-1230 branch 3 times, most recently from e13b7e5 to e2b5862 Compare June 14, 2023 19:08
@wilwade wilwade force-pushed the chore/update-comp-metadata-docker-1230 branch from e2b5862 to c591bcb Compare June 15, 2023 12:43
wilwade added 3 commits June 15, 2023 18:10
Tested with: docker run --platform=linux/amd64 --pull always --network host jacogr/polkadot-js-tools:0.55.3 metadata wss://1.rpc.frequency.xyz wss://rpc.rococo.frequency.xyz
Working dir

Fix bin dir
@wilwade wilwade force-pushed the chore/update-comp-metadata-docker-1230 branch from f2fbf5d to c94a44d Compare June 15, 2023 18:12
@wilwade wilwade temporarily deployed to github-pages June 15, 2023 20:27 — with GitHub Actions Inactive
@wilwade wilwade marked this pull request as ready for review June 15, 2023 20:31
@wilwade wilwade requested a review from demisx as a code owner June 15, 2023 20:31
@wilwade wilwade enabled auto-merge (squash) June 15, 2023 22:00
@@ -517,40 +526,48 @@ jobs:
run: |
chmod 755 $TEST_BIN_FILENAME
chmod 755 $REF_BIN_FILENAME
- name: Docker network
run: docker network create net-${{env.RELEASE_BRANCH_NAME}}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty slick. I like this idea. Wondering if this approach may help us to resolve running docker in docker issues... 🤔

Copy link
Collaborator

@demisx demisx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice 👍🏻 . I've noticed that it contains my changes from unreleased PR that I haven't yet tested with all release scenarios (full release, UI triggered, etc.). But my changes are trivial and I will re-test them in #1601

@@ -153,7 +155,8 @@ jobs:
matrix:
# This job intermittently fails on EKS runners and must be run on standalone until
# https://www.pivotaltracker.com/story/show/185045683 is resolved.
os: [[self-hosted, Linux, X64, build]]
# os: [[self-hosted, Linux, X64, testing, v2], [self-hosted, Linux, ARM64, testing, v2]]
os: [[self-hosted, Linux, X64, testing, v2]]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the purpose of "testing" and "v2"?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are the new eks runners.

run: |
CMD="docker run --pull always --network host frequencychain/polkadot-js-tools:v0.52.29 metadata ws://localhost:9946 ws://localhost:9944"
CMD="docker run --pull always --net=net-${{env.RELEASE_BRANCH_NAME}} jacogr/polkadot-js-tools:0.55.3 metadata ws://ref-node:9944 ws://test-node:9944"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you specify "--pull always" to get the latest version, do you still need to specify 0.55.3?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

--pull always doesn't affect the version that gets pulled. It specifies to always pull the image regardless of whether or not the image is already cached locally.

Copy link
Collaborator

@mattheworris mattheworris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me 🚀

@wilwade wilwade merged commit 517cb2b into main Jun 15, 2023
@wilwade wilwade deleted the chore/update-comp-metadata-docker-1230 branch June 15, 2023 22:56
shannonwells pushed a commit that referenced this pull request Apr 16, 2024
# Goal
The goal of this PR is to upgrade the polkadotjs tools for metadata
comparison.

Closes #1230 

This also includes PR #1601 for expediency. So also part of #1362

Ended up needing to run each one in a docker container with a new docker
network. This allowed everything to talk correctly.

# Checklist
- [x] Tested with: make start + docker run --rm --platform=linux/amd64
--pull always jacogr/polkadot-js-tools:0.55.3 metadata
wss://1.rpc.frequency.xyz ws://host.docker.internal:9944
- [x] Tested with test release Running:
https://github.com/LibertyDSNP/frequency/actions/runs/5282806513

---------

Co-authored-by: Dmitri <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade to latest polkadot-js/tools
4 participants