Yicong-Huang opened a new pull request, #4521:
URL: https://github.com/apache/texera/pull/4521
### What changes were proposed in this PR?
Adds two missing caches to the `scala` job in
`.github/workflows/github-action-build.yml`:
1. **pip cache** — turns on `actions/setup-python@v6`'s built-in `cache:
'pip'`, keyed on `amber/requirements.txt` and
`amber/operator-requirements.txt`. The `Install dependencies` step is currently
~1m 21s on every run because every wheel is fetched fresh.
2. **sbt build cache** — `coursier/cache-action` only caches resolved
dependency jars; it doesn't touch the zinc incremental-compile state or
scalapb-generated sources. An `actions/cache@v4` step caches
`**/target/scala-2.13/{classes,zinc,src_managed}` and `~/.sbt/1.0/zinc`, keyed
on a hash of `*.scala`, `*.java`, `*.sbt`, `project/**`, and
`**/src/main/protobuf/**`. `restore-keys` lets partial source changes fall back
to the closest cache so zinc only recompiles the changed files.
No test or build logic changes; only workflow-level caching.
### Any related issues, documentation, discussions?
Closes #4519. Companion to #4508 (which combined the two lint sbt
invocations).
### How was this PR tested?
CI on this PR — first run will populate the caches, the second push to the
branch (or a quick empty re-run) should show the speed-up. Estimated saving 2–3
minutes on cache hit (1m 21s pip + 1–2m sbt compile).
The cache key uses `hashFiles`, which is the standard pattern; if any
tracked file changes, the build still happens fresh, just from the closest
restore-key fallback.
### 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]
