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: update internal testnet reset workflow #2035

Merged
merged 2 commits into from
Oct 17, 2024
Merged

Conversation

pirtleshell
Copy link
Member

@pirtleshell pirtleshell commented Oct 17, 2024

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:

  1. A commit to master triggers a successful CI run AND the files in ci/kava-internal-testnet have changed
  2. The workflow is manually triggered via the Github Actions UI

note the above differs from protonet, which deploys on any commit to master. even with KAVA.VERSION pinned to master, the network will not redeploy on new commits because the files in ci/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.

@nddeluca
Copy link
Member

🚀

on:
workflow_run:
workflows: [Continuous Integration (Kava Master)]
types:
- completed
workflow_dispatch:

jobs:
Copy link
Member

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

Comment on lines +32 to +34
if: |
github.event_name == 'workflow_dispatch' ||
(github.event_name == 'workflow_run' && github.event.workflow_run.conclusion == 'success' && needs.changed_files.outputs.changedInternalTestnetConfig == 'true')
Copy link
Member Author

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:

  1. 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.
  2. 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 to KAVA.VERSION or the genesis file trigger an automated reset

@pirtleshell pirtleshell merged commit e951240 into master Oct 17, 2024
15 checks passed
@pirtleshell pirtleshell deleted the rp-internal-testnet branch October 17, 2024 21:43
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.

2 participants