Google Git
Sign in
cos / mirrors / cros / chromiumos / infra / proto / 34f6e09ffa71309ad5ebdc01b7e7588c724ee504
commit34f6e09ffa71309ad5ebdc01b7e7588c724ee504[log] [tgz]
authorSloan Johnson <sloanjohnson@google.com>Wed Mar 02 01:00:00 2022 +0000
committerCommit Bot <commit-bot@chromium.org>Tue Mar 15 19:30:01 2022 +0000
treeb731efa900d833294332b454fa4905b498f7a1ab
parent88480032cdf7d5a451febafc23427fc9a79598cd [diff]
Build API TestService: Add endpoint to execute rules_cros tests

BUG=b:217770417
TEST=Pass CQ & Run endpoint from commandline

Cq-Depend: chromium:3499544
Change-Id: Ifb399452ca61b5d146aa2616e0649904498f7bc4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3498755
Reviewed-by: Chris McDonald <cjmcdonald@chromium.org>
Reviewed-by: Alex Klein <saklein@chromium.org>
Commit-Queue: Sloan Johnson <sloanjohnson@google.com>
4 files changed
tree: b731efa900d833294332b454fa4905b498f7a1ab
  1. extern/
  2. gen/
  3. go/
  4. infra/
  5. recipes/
  6. src/
  7. .gitattributes
  8. .gitignore
  9. buf.yaml
  10. generate.sh
  11. LICENSE
  12. OWNERS
  13. PRESUBMIT.cfg
  14. PRESUBMIT.py
  15. README.md
  16. setup_cipd.sh
  17. unblocked_terms.txt
README.md

infra/proto

infra/proto vs chromite/infra/proto

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.