Skip to content

[CI] Reduce CI test usage #1188

@xborder

Description

@xborder

Describe the enhancement requested

The current Test GitHub Actions workflow spends a large amount of runner time repeatedly compiling the same Maven reactor across the matrix.

  • Today, most jobs run build.sh followed by test.sh. build.sh runs a full mvn clean install -DskipTests, then test.sh runs mvn clean test, which deletes the build outputs and recompiles before running tests.
  • JNI/C Data jobs add additional Maven test invocations and native build work, so some jobs compile or build equivalent artifacts multiple times.
  • For macOS and Windows runners, Java bytecode is compiled again even though the project targets maven.compiler.release=17, making the compiled classes portable across JDK 17+ and across OS/architecture for pure Java tests.
  • Other smaller inefficiencies:
    • The workflow can run twice for PR branch updates because both push and pull_request triggers fire.f
    • Integration is not required for every PR, but currently participates broadly in the workflow.

This was triggered by https://lists.apache.org/thread/drf0o5kzg1zfmok7gc09k8qz8hh9ymvh

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions