Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / 01c02f054114388ea9f44d6ae38a01d2472a50f7
commit01c02f054114388ea9f44d6ae38a01d2472a50f7[log] [tgz]
authorJack Neus <jackneus@google.com>Fri Oct 06 20:02:48 2023 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Oct 06 20:13:01 2023 +0000
treef980f3355e9c7f3f92216c980dcf3df44617ed3b
parenta603eb5751a34bb142f5976e1d0b214bcec70088 [diff]
signing: add channel to ArchiveArtifacts

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

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