Google Git
Sign in
cos / mirrors / cros / chromiumos / infra / proto / 55980c44ef6286ac60eab6f2322a54fef8ed0f57
commit55980c44ef6286ac60eab6f2322a54fef8ed0f57[log] [tgz]
authorBoris <boris.lok@cienet.corp-partner.google.com>Tue Mar 19 07:26:57 2024 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 09 09:09:33 2024 +0000
tree7941129075d38112dccfbc5abedde2e090d77c71
parent9d7e2e434019697a9ef9b26b6979c74e75670628 [diff]
[Refactoring] Change `address` to `hostname` when a user updates
the pools. Change `addresses` to `hostnames` when a user adds the pool.

BUG=None
Test=manual

Change-Id: I3299c05da061d063a0772b25ea37dbb8124f5f8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5376385
Reviewed-by: Michal Matyjek <mmatyjek@google.com>
Commit-Queue: Michal Matyjek <mmatyjek@google.com>
3 files changed
tree: 7941129075d38112dccfbc5abedde2e090d77c71
  1. bin/
  2. extern/
  3. gen/
  4. go/
  5. infra/
  6. recipes/
  7. src/
  8. .gitattributes
  9. .gitignore
  10. buf.yaml
  11. generate.sh
  12. LICENSE
  13. OWNERS
  14. OWNERS.tse
  15. PRESUBMIT.cfg
  16. PRESUBMIT.py
  17. README.md
  18. setup_cipd.sh
  19. 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.