FR: Cache Bazel version history #442
Labels
help wanted
Needs help from external contributors
P2
We'll consider working on this in future. (Assignee optional)
type: feature request
New feature or request
During working on #438 we found out that Bazelisk spends too much time on retrieving the Bazel version history (a process that happens every time we use a relative Bazel version identifier).
The GitHub repo implementation already caches the history for one hour (https://github.com/bazelbuild/bazelisk/blob/master/httputil/httputil.go#L241). We should implement something similar for GCS.
The text was updated successfully, but these errors were encountered: