Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / refs/heads/stabilize-15300.B
commit60515b4142d8bde6a094327d808346d165ea6900[log] [tgz]
authorJack Neus <jackneus@google.com>Wed Dec 21 02:07:03 2022 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Dec 21 14:06:13 2022 +0000
treee7b867f70d4e19c9c186300c5f7dfe0591ab445a
parent102a4733de9a11c4bcb6fa215b2cf3efc81cb458 [diff]
Move RetryStep enum to infra/proto

Want to be able to use this proto in Golang as well.

BUG=b:262388770
TEST=./generate

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