zhengruifeng commented on code in PR #57083: URL: https://github.com/apache/spark/pull/57083#discussion_r3548163629
########## .github/workflows/build_infra_images_cache.yml: ########## @@ -20,6 +20,13 @@ name: Build / Cache base image on: + # Rebuild cache on a schedule to keep it warm despite base image drift. + # The `ubuntu:noble` tag is re-pointed to a new image roughly monthly, + # which invalidates all cached layers built on top of it. Without a + # scheduled rebuild, the cache goes stale between Dockerfile changes + # and every commit on every PR spends ~50 minutes building base images! + schedule: + - cron: '0 4 * * *' Review Comment: I think it is a good idea, but I feel it might be too often, maybe a weekly refresh is enough? I asked AI to analyze the frequency: ``` Actual run history on master (from the GitHub Actions API) 108 runs over the last ~13 months (2025-06-03 → 2026-07-07; older runs are aged out by GitHub's ~400-day API retention). All 108 were push-triggered — confirming no scheduled refresh. ┌─────────────────────────────────┬───────────┐ │ Metric │ Value │ ├─────────────────────────────────┼───────────┤ │ Avg runs/month │ ~8.3 │ ├─────────────────────────────────┼───────────┤ │ Median gap between runs │ ~1 day │ ├─────────────────────────────────┼───────────┤ │ Mean gap │ ~3.7 days │ ... ``` -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
