Repository navigation
CI: build the engine jars from source on demand - #141
Merged
Merged
Conversation
…rkflow, engine-from-source input) (#140) Verification builds of an upstream fix at its merge commit and the engine of a branch under test (an upstream sync) now build on GitHub's runners, from source, instead of on the laptop or from upstream's moving snapshot image. build-engine-jars.yml builds the package module at any repository and ref and uploads the full lib directory; the bindings and examples workflows take an engine-from-source input that does the same for the commit they test. Push and pull_request runs keep the image path. Fixes #140 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DeKEhHXJTy1H1GgbfBZ8mL
This was referenced Oct 4, 2026
tae898
added a commit
that referenced
this pull request
Oct 6, 2026
…_jvm_payload.py stays out of the upstream pull request, workflow comments name this repository (#205) (#206) The first sync since #141 would prune build-engine-jars.yml. test_jvm_payload.py needs benchmarks/experiments, which never crosses, so upstream would skip both tests. Claude-Session: https://claude.ai/code/session_01Ubz3m6QXHESerCkehC1qgi Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #140.
New
build-engine-jars.yml(workflow_dispatch with any repository and ref, and workflow_call): builds thepackagemodule (the same jar set the Docker image carries in/home/arcadedb/lib) on JDK 21 and uploads the lib directory asarcadedb-libwith a BUILD-INFO.txt (commit, jar count, the engine manifest). Use:gh workflow run build-engine-jars.yml -f repository=ArcadeData/arcadedb -f ref=<merge sha>, thengh run download <run> -n arcadedb-lib.test-python-bindings.ymlandtest-python-examples.ymltake anengine-from-sourceinput (workflow_dispatch and workflow_call, default false): when set, the jar job builds the package module from the tested commit instead of pullingarcadedata/arcadedb:<version>, so a sync branch is tested against the engine it merged. Push and pull_request runs never take that path.Checked locally: the three files parse, pre-commit passes, every action is SHA-pinned (the same pins the other workflows use), and actionlint adds only info-level SC2012 notes in the new steps (the style the existing jar step already has). The new workflow can only be dispatched once it is on main, so its first real run is a dispatch after the merge.
🤖 Generated with Claude Code
https://claude.ai/code/session_01DeKEhHXJTy1H1GgbfBZ8mL