-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
use local copy of install_avalanchego_release.sh #557
use local copy of install_avalanchego_release.sh #557
Conversation
Co-authored-by: bernard-avalabs <53795885+bernard-avalabs@users.noreply.github.com> Signed-off-by: Ian Suvak <ian.suvak@avalabs.org>
@@ -0,0 +1,133 @@ | |||
#!/usr/bin/env bash |
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.
We once had this copied over from subnet-evm
, but got rid of it for some reason. Are we not able to use the file directly from our submodule while setting some env vars? Would it possibly be worthwhile to make a PR to subnet-evm
to make it usable if not? Just spitballing :)
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.
We use it like this in teleporter. I think scripts like this are reasonable to have copy pastad in individual repos IMO and we do it already with other scripts. Happy to be overridden though.
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.
Oh, lol forgot which repo I was in. Can we use the one from the teleporter submodule? I don't mind copying code if its the best/easiest option, just wondering if we can piggyback somewhere here
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.
each of them uses their own versions.sh
we certainly can but then we end up with the same problem of coupling repos tighter than they need to be
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.
Yeah, that's fair, you've convinced me 😅
Why this should be merged
Allows for easier custom avalanchego vs subnet-evm versions assuming they are compatible with each other
How this works
Updates both the github e2e as well as
./scripts/e2e_test.sh
runner to use avalanchego version from./scripts/versions.sh
instead of using the version fromsubnet-evm
repo.How this was tested
Existing tests should pass.
How is this documented
Need to update README.md for the simplified flow