Google Git
Sign in
chromium / chromiumos / infra / proto / refs/heads/factory-brya-15684.B
commit5ea14a8387b374ff8a0329b47abed53ca6e2f5b2[log] [tgz]
authorTrent Apted <tapted@chromium.org>Wed Nov 15 04:42:22 2023
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Nov 17 21:12:36 2023
tree781deb79e37f60369f96d08c4e05062516547b21
parent5e0db518620ac8acb017e5e389a6dd8bd01cb789 [diff]
sdk_subtools: (proto) Add fields for populating builder summary text.

Allows summary info to surface in builder pages on successful runs.

See details in Implementation: https://crrev.com/c/5033582
Recipe: https://crrev.com/c/5028567

BUG=b:310719673
TEST=led

Change-Id: I1c57d6be0235c336e7873cdab955121986795e74
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5035878
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
Commit-Queue: Trent Apted <tapted@chromium.org>
3 files changed
tree: 781deb79e37f60369f96d08c4e05062516547b21
  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. OWNERS.tse
  14. PRESUBMIT.cfg
  15. PRESUBMIT.py
  16. README.md
  17. setup_cipd.sh
  18. 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.