Skip to content

ci: keep RWX in step with CircleCI's required checks #24048

Open

Description

@teddyknox

Part of #24044.

RWX keeps its own copy of the dependencies of CircleCI's four required gates: ci-gate, required-contracts-ci, required-rust-ci and required-rust-e2e. When a change to CircleCI alters those dependencies, someone must update RWX's copy. Until then, RWX's ci-unit-tests task fails. The RWX checks are optional, so no merge is blocked, but a red optional check teaches people to ignore RWX.

This is continuous work for as long as the shadow runs. The assignee is the owner.

When the alignment check fails

  1. Read the failure of ops/ci/migration/circle-alignment.py. It names the gate.
  2. Update ops/ci/runtime/pr-gates.json. For required-rust-e2e, update JOBS in ops/ci/runtime/rust-e2e.py, .rwx/rust-e2e.yml and e2e_gate in ops/ci/migration/circle-gates.json.
  3. Run the check again.

The operator guide, docs/ai/rwx-shadow-ci.md, has the details.

Close when

The shadow is removed, or RWX replaces CircleCI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

M-ciMeta: ci related work

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions