Skip to content

Add Superset integration CI job - #12

Merged
splasky merged 1 commit into
mainfrom
superset-integration-test
Aug 11, 2026
Merged

Add Superset integration CI job#12
splasky merged 1 commit into
mainfrom
superset-integration-test

Conversation

@splasky

@splasky splasky commented Aug 11, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add a dedicated Superset integration job to the Python CI workflow.
  • Check out apache/superset master and run Superset's Datastore DB engine spec tests against the local package checkout.
  • Use Python 3.11 for the Superset job to match current Superset support.
  • Install Superset system dependencies required by native development dependencies such as python-ldap.

Test scope

This PR intentionally runs the targeted Superset Datastore integration tests instead of the full Superset test suite on every package change. The full upstream suite is broad, slow, and can fail for unrelated frontend, service, database, or environment reasons. The targeted Datastore engine tests provide the relevant blocking signal for python-datastore-sqlalchemy compatibility.

Validation

  • GitHub Actions Python CI passed on branch superset-integration-test, run 31508057525.
  • build job passed.
  • superset-integration job passed.

Comment thread .github/workflows/python-ci.yaml
Comment thread .github/workflows/python-ci.yaml
Run a dedicated Superset integration job in GitHub Actions so changes to python-datastore-sqlalchemy are validated against Apache Superset's Datastore DB engine spec tests.

The job checks out apache/superset master, uses Python 3.11 to match current Superset support, installs Superset development dependencies with uv, installs this package from the workflow checkout, initializes the Superset test database, and runs tests/integration_tests/db_engine_specs/datastore_tests.py.

Install libldap2-dev, libsasl2-dev, and libssl-dev because Superset development dependencies include native packages such as python-ldap that require system headers on GitHub's Ubuntu runners.

Keep the Superset validation targeted instead of running the full Superset suite on every package PR. The full upstream suite is broad and can fail for unrelated frontend, service, or environment issues; targeted Datastore engine tests provide the relevant blocking signal for this package.
@splasky
splasky force-pushed the superset-integration-test branch from e64f896 to 29addcc Compare August 11, 2026 15:54
@splasky
splasky marked this pull request as ready for review August 11, 2026 15:57
@splasky
splasky merged commit ede0634 into main Aug 11, 2026
2 checks passed
@splasky
splasky deleted the superset-integration-test branch August 11, 2026 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant