Google Git
Sign in
chromium / chromiumos / infra / proto / 92445a11f2c20debd68e6a45d0e62f5929a4e5ad
commit92445a11f2c20debd68e6a45d0e62f5929a4e5ad[log] [tgz]
authorOtabek Kasimov <otabek@google.com>Thu Jul 11 06:05:03 2024
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 11 15:28:27 2024
treef0965bf88e071c3f0a7fc5643be72f81bb714516
parent3cdabac47806be520b9ee96e37ca62c205b87377 [diff]
configs: Add new proto for lab recovery-versions

BUG=b:352455603
TEST=run regenerate.sh

Change-Id: I1131e16c49c421a42b23a3658cded585db3d944f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5691722
Commit-Queue: Chris DeLaGarza <cdelagarza@google.com>
Reviewed-by: Chris DeLaGarza <cdelagarza@google.com>
Auto-Submit: Otabek Kasimov <otabek@google.com>
3 files changed
tree: f0965bf88e071c3f0a7fc5643be72f81bb714516
  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.