Yicong-Huang opened a new pull request, #4638: URL: https://github.com/apache/texera/pull/4638
### What changes were proposed in this PR? Trim the redundant compile in the scala job and reorder steps so cheap lints fail fast. Concrete changes in `build.yml`: - Drop the `Compile with sbt: sbt clean package` step. Its `package` output was not consumed by any later step, and the preceding dist step already compiled every module — this saves the ~1m 26s the step took on a clean run. - Drop the leading `clean;` from `Build distributable bundles for license check` so the dist build can reuse the earlier sbt step's compile output instead of throwing it away. - Move `Lint with scalafix` up to run right after `Lint with scalafmt`, before `Build distributable bundles`. scalafix forces a full compile; dist now consumes that compile incrementally. - Move `Install dependencies` (pip) down to run just before `Run backend tests` since only the test step needs the python deps. Lint and dist failures no longer pay for the install. Resulting per-event order: ``` ... checkout / JDK / Python / sbt setup / coursier cache ... - Lint with scalafmt - Lint with scalafix # forces compile, fail-fast on lint - Create Databases - Build distributable bundles # reuses scalafix's compile, no `clean` - Unzip / license check / audit - Install dependencies # pip, only needed by tests - Create texera_db_for_test_cases - Set docker-java API version - Run backend tests ``` ### Any related issues, documentation, discussions? Closes #4637. Step timings on the run that motivated this PR (`25239784635`, scala job ~14m 44s) called out the wasted `Compile with sbt` (1m 26s) and the trailing scalafix that delayed lint feedback until after the dist build. ### How was this PR tested? Will be exercised by this PR's own scala matrix on CI. Each individual step (scalafmt, scalafix, dist, license check, audit, tests) is unchanged in invocation; only their ordering and the removal of the redundant `sbt clean package` differ. uv pip migration is independent and lives in #4636. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude 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]
