Skip to content
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

Merged
merged 4 commits into from
Nov 20, 2024

Conversation

iansuvak
Copy link
Contributor

@iansuvak iansuvak commented Nov 20, 2024

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 from subnet-evm repo.

How this was tested

Existing tests should pass.

How is this documented

Need to update README.md for the simplified flow

@iansuvak iansuvak marked this pull request as ready for review November 20, 2024 14:33
@iansuvak iansuvak requested a review from a team as a code owner November 20, 2024 14:33
@iansuvak iansuvak mentioned this pull request Nov 20, 2024
README.md Outdated Show resolved Hide resolved
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
Copy link
Contributor

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 :)

Copy link
Contributor Author

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.

Copy link
Contributor

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

Copy link
Contributor Author

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

Copy link
Contributor

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 😅

@iansuvak iansuvak merged commit e8ed8fe into validators_at_proposed Nov 20, 2024
8 checks passed
@iansuvak iansuvak deleted the use-local-avalanchego-versions branch November 20, 2024 17:59
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants