mengw15 opened a new pull request, #6274: URL: https://github.com/apache/texera/pull/6274
### What changes were proposed in this PR? The platform services' build jobs (the `platform` matrix) provision only postgres. A boot smoke test there can't fully start a service that needs more — `file-service` fail-fasts on **MinIO + LakeFS** during `run()` (S3 bucket creation + `LakeFSStorageClient.healthCheck()`), so it can only be checked shallowly. This PR adds a **`platform-integration` job** (mirroring `amber-integration`) that provisions **postgres + MinIO + LakeFS** and boots each packaged platform service from its dist, asserting it reaches a listening state without a runtime classpath/linkage crash (via `.github/scripts/smoke-boot.sh`, from #6220). Every service has its real dependencies here, so all run in **strict** mode — `file-service` included. - Dists are shipped in as **CI artifacts** from the `platform` job (`upload-artifact` → `download-artifact`), not rebuilt. - Infra is provisioned **once for the whole tier** (single job), like `amber-integration`. - **Ubuntu-only**, matching the `platform` job's OS scope. (`amber-integration` is cross-OS because its Python-UDF / native specs are arm64-mac-sensitive; these boot checks are pure-JVM and OS-independent.) This is the infra-provisioned home for the platform services' integration checks (#6273); the boot smoke test is its first inhabitant, and future platform integration tests (e.g. `file-service`'s S3 / LakeFS paths) can live here too. ### Any related issues, documentation, discussions? Closes #6273. The boot smoke test script is from #6220. Extracting the shared infra provisioning into a composite action shared with `amber-integration` (DRY) is deferred to #6047. ### How was this PR tested? - LakeFS provisioning recipe validated locally (postgres + MinIO + LakeFS via docker) → LakeFS reaches healthy in ~9s. - Confirmed `storage.conf` defaults align with the provisioned endpoints (S3 `http://localhost:9000`, LakeFS `http://localhost:8000/api/v1`, JDBC `localhost:5432`), so each service boots against this infra with no extra env. - `smoke-boot.sh` was validated end-to-end in #6271 (config-service + texera-web reached LISTEN in CI; the negative case caught a reintroduced #6206 Arrow / Jackson boot crash). - `--network host` reachability, the artifact flow, and each service's strict boot are exercised by this workflow's own CI run. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-opus-4-8) -- 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]
