mengw15 commented on PR #6274: URL: https://github.com/apache/texera/pull/6274#issuecomment-4929419903
Thanks @Yicong-Huang — all three are addressed in `b197f29`: **1. Label trigger.** Added a dedicated `run_platform_integration` input mirroring `run_amber_integration` end-to-end (LABEL_STACKS → `decide` output → precheck output → both `build.yml` callers → the job's `if:`), triggered by the same labels as `platform` (`platform` / `common` / `ddl-change` / `ci`). It's also a proper *superset* of platform's trigger, exactly as `amber-integration` is of `amber`: a dedicated `platform-integration` label fires only the integration stack, so a future spec-only change can run it without the full `platform` job. No labeler rule applies that label yet — platform has no integration specs today (#6047) — so it's a forward hook for now. **2. Per-service matrix.** `platform-integration` is now a per-service `matrix.include` (the same 6 services as `platform`), one boot check per service. Latest CI shows the six `platform-integration (<service>)` legs. **3. No artifacts / parallel.** Dropped the `upload`/`download-artifact` hand-off and `needs: platform`; the two jobs run in parallel now. Rather than the shared `build` job, I made `platform-integration` fully independent — it builds each service's dist on its own classpath and boots it — mirroring how `amber-integration` compiles its own tests independently of `amber`. That keeps it **artifact-free** (a shared `build` job would reintroduce an `upload`/`download` hand-off) and matches the existing amber/amber-integration shape. The trade-off is a second compile per service (as `amber` and `amber-integration` each compile today), in exchange for zero artifacts and full parallelism. All six `platform-integration` legs are green on `b197f29`: `file-service` boots against real MinIO + LakeFS and reaches LISTEN on :9092, and because the jobs are independent, a `platform-integration` leg finishes before the same service's `platform` leg (they run in parallel). -- 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]
