karthik-0306 opened a new pull request, #12857:
URL: https://github.com/apache/seatunnel/pull/12857
### Purpose of this pull request
Related to #12707.
No GitHub workflow runs the tests under `tools/seatunnel-python-sdk` today.
The only Python workflow, `cli.yml`, is limited to `seatunnel-cli/**`. As a
result, the existing `test_sdk.py` and the new `test_java_detector.py` (added
in #12740) only run when someone runs them locally. This was pointed out during
the review of #12740, and @SEZ9 agreed on #12707 that it should be a separate,
small PR.
This PR adds `.github/workflows/python-sdk.yml`, modeled on `cli.yml`:
- Runs only when `tools/seatunnel-python-sdk/**` or the workflow file itself
changes, on pull requests and on pushes to `dev`.
- Runs `pytest` on Python 3.9 (the `python_requires` floor in `setup.py`)
and 3.13 (a current release).
- Steps: `pip install -e . pytest`, then `python -m pytest tests -v`.
- Read-only `contents` permission, a concurrency group that cancels
superseded runs, and a 15-minute timeout.
No lint job is added, because the SDK has no ruff configuration yet. Adding
one is out of scope here.
### Does this PR introduce _any_ user-facing change?
No. This is a CI-only change. No SDK code, engine code, configuration, or
documentation is modified.
### How was this patch tested?
- Ran the workflow's steps locally in a fresh virtualenv from
`tools/seatunnel-python-sdk/`:
```bash
python -m pip install -e . pytest
python -m pytest tests -v
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
