| commit | cfdcf6e9f7a4ad3c010f7d7e4c1b7ece749300b4 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Fri Oct 07 17:31:54 2022 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Oct 08 00:39:36 2022 +0000 |
| tree | 8335ef94a58b19d2e9b134830a68c1e469619de5 | |
| parent | a6f0e0e4403a5883e0452178f3b66d190bc71bea [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8800916427080344289 recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/15dba9dcd3a474b6cdc00bd5529888dc8e78432b 15dba9d (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 51ba99a32514 to d1b47703248e Please check the following references for more information: - autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller - rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback - cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md Use https://goo.gl/noib3a to file a bug. Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: Ib1cd32b04d33b8ec23a95a6c415de90af9c08feb Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3939196 Bot-Commit: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>
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.