Skip to content

Add CI task to verify peer connectivity #526

Description

@rootulp

Context

There are several open PRs that add/remove/modify a peer address in peers.txt. Examples:

  1. Change of peer Cumulo #525
  2. Updating Spidey Peer after migrating Validator node due to hardware issues. #524
  3. Update peer #521
  4. Add W3 to peers. #519
  5. Add kjnodes seed and peer node #509
  6. Add AM Solutions seed #508
  7. Adding figment's peer #507

Problem

It's not immediately obvious how to verify the correctness of these PRs

Proposal

Add a CI check that verifies if a peer is accessible and running on the network that corresponds to the peers.txt that was modified in the PR.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions