| commit | fe9ad4e4509f174f27c4bd4990ceace1f3b0c1d7 | [log] [tgz] |
|---|---|---|
| author | Jack Neus <jackneus@google.com> | Mon Jun 27 20:00:07 2022 +0000 |
| committer | Jack Neus <jackneus@google.com> | Fri Jul 08 15:23:25 2022 +0000 |
| tree | ffe244d5eedbac3c6b88625c72d677c635be5875 | |
| parent | f47843d7b3b489472eb0baf9c77ed2d2b8ca60f4 [diff] |
Add ToolchainsRequest and ToolchainsResponse BAPI protos Rubik builds need a way to get toolchain info, wrapping existing GetToolchainTupleForBoard method in a BAPI endpoint. BUG=b:237098403 TEST=./generate Change-Id: If5e0a5a32b255c696fdd09f3ade3c220a324cb2d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3727118 Commit-Queue: Jack Neus <jackneus@google.com> Reviewed-by: George Engelbrecht <engeg@google.com> Reviewed-by: Madeleine Hardt <hardtmad@google.com> (cherry picked from commit 793af242e5e991de6ff6d890c38be903dca2ca69) Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3752956 Auto-Submit: Jack Neus <jackneus@google.com> Reviewed-by: Benjamin Shai <bshai@google.com> Commit-Queue: Benjamin Shai <bshai@google.com>
This repository exists in two locations in the tree: infra/proto, and chromite/infra/proto. The infra/proto repository is always at ToT, while the chromite/infra/proto checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.
When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto checkout. Chromite generates its proto bindings from the chromite/infra/proto repo.