Open
Conversation
fresh-borzoni
force-pushed
the
feat/elixir-ci
branch
from
badea2b to
532f626
Compare
Contributor
Author
|
@luoyuxia @leekeiabstraction PTAL 🙏 filled jira for infra: https://issues.apache.org/jira/browse/INFRA-27826 and once it's resolved, follow up with standard action. |
7 tasks
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.
closes #459
The Elixir bindings have no CI. So this PR adds a GitHub Actions workflow for bindings/elixir/** that mirrors what Python and C++ already have: compile the NIF via mix compile --warnings-as-errors, run formatting and lint checks (mix format --check-formatted, mix credo), run unit tests via mix test, and run integration tests against a real Fluss cluster started through the shared fluss-test-cluster CLI binary. Path-ignore rules on the existing Rust/C++/Python workflows should be updated so Elixir-only changes don't trigger them.
Scope of this issue is the test pipeline only. Release-side concerns - precompiled NIF artifacts for linux/macOS and publishing to Hex are tracked separately in the follow-up release-pipeline issue.
Assumptions and limitations: