Google Git
Sign in
cos / mirrors / cros / chromiumos / infra / proto / be5b2267c58d946f56f99d32ae17859d85f7fa51
commitbe5b2267c58d946f56f99d32ae17859d85f7fa51[log] [tgz]
authorJack Neus <jackneus@google.com>Mon Sep 12 00:49:01 2022 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Sep 12 14:14:49 2022 +0000
tree8425d58f9aa476e119405e0fd8aef906f3fbca28
parent7158e6496d5a1817db5a428afcd8a8e80f168f3e [diff]
proto: add IMAGE_TYPE_NETBOOT

BUG=b:239795601
TEST=./generate

Change-Id: I2d07293d0fd01c0894fbf19f35933eae4ad8f034
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3890270
Commit-Queue: Jack Neus <jackneus@google.com>
Commit-Queue: George Engelbrecht <engeg@google.com>
Reviewed-by: George Engelbrecht <engeg@google.com>
Auto-Submit: Jack Neus <jackneus@google.com>
3 files changed
tree: 8425d58f9aa476e119405e0fd8aef906f3fbca28
  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.