Skip to content

CI tests partitioning #1624

@sergiimk

Description

@sergiimk

During #599 we disabled engine tests to avoid pulling huge container images. Meanwhile the number of components we need integration tests for continues to increase (DBs, Elastic, IPFS, blockchains, etc.) and we need a more scalable solution.

Proposed solution:

  • Build tests without running
  • Use nextest arcive to save artifacts
  • Spawn a matrix job that:
    • Downloads test archive
    • Runs different categories of tests on different instances

This approach should allow us to:

  • Speed up our CI via parallelism
  • Solve disk space issue
    • Remove the "Maximize build space" step that takes ~1min
  • Restore engine tests in CI

Metadata

Metadata

Assignees

No one assigned

    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