Try out buildstream remote execution support as a replacement for the current cache
Context
We can use remote execution API's to have remote cache, instead buildstream internal implementation
https://github.com/bazelbuild/remote-apis
Benefits
- Using remote-apis for remote cache will be the default for buildstream 2.0; It's in our interest to have a consistent piece of infra that supports both bst-1 and bst-2
- For the above, It's also in our interest try to help improve buildstream support with the rest of the remote-apis ecosystem
- In the future, we can maybe use the RE capabilities to accelerate the builds
- This will allow us to simplify as same infra can be used for cache and to run the builds
Description
- Let's start with a testing branch to get data and see possible problems
-
Two testing approaches:Keeping compatibility with bst-1: !2389 (closed)Use builstream master (2.0): !2378 (closed)
- buildstream 1.6 added support for remote apis, so we can use that directly
Acceptance Criteria
-
new cache remote server is deployed using some of the remote API - based implementations: freedesktop-sdk/infrastructure/artifacts!1 (merged) -
freedesktop-sdk is using it
Edited by Javier Jardón