Skip to content
This repository was archived by the owner on Nov 21, 2026. It is now read-only.
This repository was archived by the owner on Nov 21, 2026. It is now read-only.

CI: build engine jars from source (verification builds and branch tests) instead of on the laptop #140

Closed

Description

@tae898

The laptop's cores are reserved for timing work (performance hunts, the pin-vs-main refresh). Two kinds of build still ran there: (1) after every upstream fix merge, a Maven build of the engine and plugins at the merge commit to verify our filed repros (about ten a day, 3-5 minutes each); (2) before a sync, a local wheel build and the full bindings suite, because our CI downloads the engine jars from upstream's moving snapshot image (arcadedata/arcadedb:<version>), not from the engine source on the branch being tested, so it cannot test a sync's merged engine exactly. Proposed: a build-engine-jars workflow (workflow_dispatch: any repository and ref; workflow_call) that builds the package module and uploads the full lib directory, and an engine-from-source input on the bindings and examples test workflows that builds the engine from the tested commit's source instead of pulling the image. Push and pull_request runs keep the image path unchanged.

Activity

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

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