You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 7, 2022. It is now read-only.
We can start with local clusters using the current tooling for testing on CI.
For every pull request we should create a local deployment. When we tag a new release we should also deploy on remote using a minimal deployment (first create the config file, it should be composed of 3 nodes running on aws, gcp and azure with monitoring enabled).
We can start with local clusters using the current tooling for testing on CI.
For every pull request we should create a local deployment. When we tag a new release we should also deploy on remote using a minimal deployment (first create the config file, it should be composed of 3 nodes running on aws, gcp and azure with monitoring enabled).
For the local deployment we should check that blocks are being produced and finalized (see https://github.com/w3f/polkadot-deployer/blob/master/lib/benchmarks/strategies/finality.js) for how we do this on benchmarks.
For the remote deployment we should check block production, finalization and also the monitoring endpoints (grafana and substrate-telemetry).
The text was updated successfully, but these errors were encountered: