[beproxy] connect ResultStore, create invocation Connect to ResultStore service with grpc. Create an Invocation, and do nothing else. resultstore.go: ResultStoreUploader will be the interface for pushing data up through grpc calls. client.go: contains a ResultStoreUploader. main.go: sets up invocation parameters from command-line flags. scripts/bes-ninja-wrapper.sh: minimalist wrapper that coordinates beproxy lifetime with a wrapped ninja (or any command) invocation. Test: none yet, pending corresponding ninja tool changes Bug: 390427892 Change-Id: I3a32a5ad87e4f4aec00370442b7586ca8d45949b Reviewed-on: https://fuchsia-review.googlesource.com/c/rsclient/+/1341881 Commit-Queue: David Fang <fangism@google.com> Reviewed-by: Jay Zhuang <jayzhuang@google.com>
The rsclient repository contains tools that support the use of ResultStore services and API.
rsproxy acts as a bridge between build tools and the ResultStore service.
The first supported build tool is Fuchsia's fork of ninja.
rsclient builds with Bazel. We recommend using Bazelisk to use the version of Bazel currently supported by this code base.rsclient is supported for Linux, and is yet untested on other platforms.
Before working with the code base, we recommend installing the precommit hook once per git clone with:
./scripts/install_precommit.sh
This runs a variety of checks and automatic regeneration steps for you before committing local changes.
To build everything:
$ bazelisk build ...
To run tests:
$ bazelisk test ...
Not yet applicable.
Not yet applicable.