Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / refs/heads/stabilize-15083.B
commit0724795e8b769f44c13d47251600a3574c9c2232[log] [tgz]
authorLizzy Presland <zland@google.com>Fri Aug 05 16:52:31 2022 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Aug 30 19:09:42 2022 +0000
tree9d473d47831351abcaacf84667acf846a623e492
parent1c352a4c9b38a6f08b32fa52d4e0f4846ba15e29 [diff]
observability: Record apparent & disk util sizes

BUG=b:224589938
TEST=./generate.sh

Change-Id: Ib628e903e3254bafb0a5a87d3f8a211b4df300fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3813043
Reviewed-by: Alex Klein <saklein@chromium.org>
Auto-Submit: Lizzy Presland <zland@google.com>
Commit-Queue: Alex Klein <saklein@chromium.org>
3 files changed
tree: 9d473d47831351abcaacf84667acf846a623e492
  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.