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

[DRAFT] Add Flextesa as a CI/CD integration test target + docs #1169

Closed
wants to merge 178 commits into from

Conversation

jevonearth
Copy link
Collaborator

@jevonearth jevonearth commented Nov 11, 2021

Improved docs, but not complete.
Made changes to config.ts. Related work in ecadlabs/tezos-key-gen-api#31 is depended on by this PR

Todo:

  • If user re-runs /flextesa-setup/deploy-flextesa-contracts.ts it does not update /integration-tests/config.ts. Impracticle if switching a sandbox between protocols.
  • The When starting flextesa, block 0 and 1 will have specific protocols to get the chain running. The flextesa setup script discovers the protocol from the current head, but if the script is run before block level 3, it will get one of the bootstrap protocols. Example for flobox
    • 0 - PrihK96nBAFSxVL1GLJTVhu9YnzkMFiBeuJRPA8NwuZVZCE1L6i
    • 1 - Ps9mPmXaRzmzk35gbAYNCAw6UXdE2qoABTHbN2oEEc1qM7CwT9P
    • 2 - PsFLorenaUUuikDWvMDr6fGBRG8kt3e3D3fHoXK1j1BFRxeSH4i

Kunal Jaiswal and others added 28 commits November 11, 2021 11:21
@Innkst Innkst linked an issue Jan 18, 2022 that may be closed by this pull request
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.

Add a flextesa node to our CI pipeline
2 participants