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

ci: integration test #36

Merged
merged 70 commits into from
Oct 3, 2023
Merged

ci: integration test #36

merged 70 commits into from
Oct 3, 2023

Conversation

fadeev
Copy link
Member

@fadeev fadeev commented Aug 18, 2023

Running some basic commands to ensure that the main bits are working fine.

  • cctx tracking: exit with 0 on success, 1 on failure
  • CCM template: interact task fix to work when using --fees zeta

@fadeev fadeev marked this pull request as ready for review August 18, 2023 12:22
@fadeev fadeev changed the title ci: integration tests ci: integration test Aug 18, 2023
@fadeev fadeev marked this pull request as draft October 1, 2023 10:12
@fadeev fadeev marked this pull request as ready for review October 1, 2023 10:13
@fadeev fadeev marked this pull request as draft October 1, 2023 10:14
@fadeev fadeev marked this pull request as ready for review October 1, 2023 10:15
@fadeev fadeev marked this pull request as draft October 1, 2023 10:15
@fadeev fadeev marked this pull request as ready for review October 1, 2023 10:19
@fadeev fadeev marked this pull request as draft October 1, 2023 10:19
@fadeev fadeev marked this pull request as ready for review October 1, 2023 10:33
@fadeev
Copy link
Member Author

fadeev commented Oct 2, 2023

@andresaiello please, review, thanks!


if grep -E "^PRIVATE_KEY=[a-fA-F0-9]{64}$" .env; then
echo "The .env file contains a valid PRIVATE_KEY entry without the 0x prefix."
rm .env
Copy link
Collaborator

@andresaiello andresaiello Oct 2, 2023

Choose a reason for hiding this comment

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

why you remove it?

Copy link
Member Author

Choose a reason for hiding this comment

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

You mean why have rm .env? The reason is in this section of the test I'm testing the key generation functionality, but I don't need the actual key for the rest of the test. I'm using a PRIVATE_KEY env variable stored in GitHub secrets, which has enough tokens (both native and ZETA) to deploy and test contracts. At some point I'll add faucet to the test, but I'll probably still keep using the evn variable, because I need native gETH, for example, which I can't get from a faucet.

@fadeev fadeev merged commit cd1637d into main Oct 3, 2023
6 checks passed
@fadeev fadeev deleted the ci/integration branch October 3, 2023 11:20
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.

Set up a Github action to run the main commands nightly
2 participants