-
Notifications
You must be signed in to change notification settings - Fork 333
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: update internal testnet reset workflow #2035
Conversation
🚀 |
on: | ||
workflow_run: | ||
workflows: [Continuous Integration (Kava Master)] | ||
types: | ||
- completed | ||
workflow_dispatch: | ||
|
||
jobs: |
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.
It's great to see re-use of the workflow jobs instead of duplicating them
if: | | ||
github.event_name == 'workflow_dispatch' || | ||
(github.event_name == 'workflow_run' && github.event.workflow_run.conclusion == 'success' && needs.changed_files.outputs.changedInternalTestnetConfig == 'true') |
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.
this is the logic for whether or not to actually reset the network.
it amounts to:
- reset network if we are manually dispatching the flow. the manual dispatch is a specific choice. if i hit the reset network button, the network should reset regardless of what the content of the HEAD commit is.
- when a commit to master passes the test CI, reset the network if the files in
ci/kava-internal-testnet
have changed. only commits that include changes toKAVA.VERSION
or the genesis file trigger an automated reset
* ci: update internal testnet reset workflow * on merge to master, only redeploy when files changed
Updates CD pipeline for internal testnet, now on newer infra. The action uses the same workflows as the protonet flow, but with different variables.
Confirmed the reset + seeding of network works by running the workflow locally.
Additionally, removed all workflows and scripts that are no longer used.
The workflow is triggered in either of these cases:
ci/kava-internal-testnet
have changednote the above differs from protonet, which deploys on any commit to master. even with
KAVA.VERSION
pinned tomaster
, the network will not redeploy on new commits because the files inci/kava-internal-testnet
will not change. if the commit is updated or the genesis file changes, the network will be reset & deployed. otherwise, the network will only be reset if the workflow is manually dispatched.