Yicong-Huang opened a new pull request, #4632: URL: https://github.com/apache/texera/pull/4632
### What changes were proposed in this PR? Add a separate, label-gated CI stack that runs only the `WorkflowCompilingService` sbt project's tests, mirroring the existing `frontend` pattern. - `.github/labeler.yml`: add a `workflow-compiling-service` label that the Pull Request Labeler attaches whenever a PR touches `workflow-compiling-service/**`. - `build.yml`: add a `workflow-compiling-service` job gated on a new `run_workflow_compiling_service` input. The job sets up JDK + sbt and runs `sbt "WorkflowCompilingService/test"` only — no postgres, no python, no license-check distros, since the resource-extension tests do not need them. - `required-checks.yml`: `precheck` now emits `run_workflow_compiling_service` (true iff the PR carries the `workflow-compiling-service` label; always true on `push`/`workflow_dispatch`). Both the `build:` and `backport:` callers pass it through. The full `scala` job is unchanged, so the WCS tests still run as part of `sbt test` there. Treat the new job as a fast-path signal that's specifically green for WCS-only PRs; pruning duplication in the `scala` job can come as a follow-up. ### Any related issues, documentation, discussions? Closes #4631 ### How was this PR tested? YAML parses locally for all three modified files (`labeler.yml`, `build.yml`, `required-checks.yml`). The job will be exercised on this PR itself: as a workflow-only PR (no `workflow-compiling-service` label), `run_workflow_compiling_service` should be `false` and the new `Required Checks / build / workflow-compiling-service` check should appear as `skipped`. Adding the `workflow-compiling-service` label and pushing should flip it to actually run `sbt "WorkflowCompilingService/test"`. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.7) -- 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]
