-
Notifications
You must be signed in to change notification settings - Fork 176
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
feat: e2e upgrade software #727
Conversation
…-upgrade-software
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work pulling this off! The code looks good to me, mostly questions
…-upgrade-software
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing work putting everything together 👏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, great work. Just some style and clarity suggestions.
- Test e2e upgrade test with current `dev` branch - 5f8af8c Applied from PRs babylonchain/babylon#730 and babylonchain/babylon#727
- Test e2e upgrade test with current `dev` branch - 5f8af8c Applied from PRs babylonchain/babylon#730 and babylonchain/babylon#727
babylonchain/babylond-before-upgrade
babylonchain/babylond
with the same state data as before, since the mounting point also writes locally, it just needs to use the same mount pathe2e-build-script
build binaries for e2e initialization of chainbuild-docker-e2e
that build docker imagesclean-docker-network
removes the network with namebbn-test
babylond-before-upgrade
called bybuild-docker-e2e
e2e-init-chain
called bybuild-docker-e2e