Skip to content

Rebuild CI #9815

Description

@natalieesk

For the CI rebuild, to decide on the architecture, we fisrst need to investigate some things:

  1. Are we going to keep the tests with cached states?
  2. Shall we keep using GCP? How do we run most of the things we’re running without relying on external providers?
  3. What's the best way to consolidate workflows?
  4. How can we build efficiently without Docker?

A/C

To have sufficient information to design the CI architecture. This research will be populated in the CI Planning document.

The following functionality needs to be in CI:

  • Unit tests
  • Integration tests
  • Linters
  • Documentation publishing
  • Formatter
  • Usable by external contributors

The following functionality should exist:

  • Code coverage
  • Stateful tests
  • Logs

The following are nice to haves:

  • Benchmarks
  • Run locally
  • Identify regressions
  • Releasing on different platforms

Metadata

Metadata

Assignees

No one assigned

    Labels

    EpicZenhub Label. Denotes a theme of work under which related issues will be grouped

    Type

    Fields

    No fields configured for Epic.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions