urlyy commented on PR #2733: URL: https://github.com/apache/fory/pull/2733#issuecomment-3388371745
> > > It seems like Bazel binary could be **cached in GitHub Actions** to avoid downloading it on every run. Is it possible to set up a cache for Bazel in our workflows? > > > > If it could, here are the benefits: > > > > > > > > 1. Faster builds: reuse Bazel binary instead of downloading every run. > > > > 2. More reliable: reduce network failures during downloads. > > > > 3. Cost saving: less CI runtime and resource usage. > > > > > > Good idea! @urlyy I can add caching as a follow-up improvement. We have two options: > > > > > > 1. GitHub Actions cache - Simple, caches the binary directly > > > 2. Bazelisk - Tool that auto-manages Bazel versions with caching > > > > > > Which do you prefer? > > > > could you open a new issue for this? I think this PR can be merged now I think Fory doesn’t seem to need managing multiple Bazel versions — caching the binary directly is enough. @chaokunyang -- 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]
