-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate bazel remote cache server with the bazel build POC #74105
Comments
Pinging @elastic/kibana-operations (Team:Operations) |
I've been thinking about this some more and while I'm really excited about Bazel in the long-term, I'm wondering if we should do something really simple in the short term for the We already have cache keys produced by It could work something like:
In CI, we would have the appropriate credentials for putting new items into the cache. cc @spalger |
It's definitely something I've suggested to folks before, I don't think it would be that hard to build, but I haven't seen any interest before now in a feature that will likely rely on some infrastructure to get right. Converting the cache key to make sure that it is totally reproducible and not reliant on the OS or repo location would be the first step. |
I think we're getting to the point where we've squeezed what we can out of the optimizer and other than removing legacy plugin discovery, I'm not sure there's a lot of low hanging fruit left to improve the start up time of Kibana when switching branches. Could be a really good Spacetime project that would have a big impact. |
I agree that this could be a big win if we get the cache key right. @spalger, would you mind creating an issue to track adding remote caching to |
I think at this point in the context of the POC we already did a lot of tests with the remote cache server. More info could be found on #69706 (comment) in the |
After setting up the kbn packages to build with bazel (#74104) we should experiment to integrate it with a remote cache server.
The text was updated successfully, but these errors were encountered: