| commit | 7ac455f8f54c7574fb522112e76c33f56dcb0643 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Wed Oct 05 18:32:54 2022 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 06 01:40:45 2022 +0000 |
| tree | 2d3e6e0caada31897f65b7d39bdde008678f1ae9 | |
| parent | 6f87eb378c86ddc2c8c5aa0ce0cb8e665e940b9a [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (chromiumos_config, recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8801093846796511665 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/e0a8ca2bde6017b3695d2e2f6cc3d804baae49ba e0a8ca2 (zhihuixie@google.com) test_result_contract: add test invocation proto recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/af504e0920ec298850ee0f17765c3c85a078644f af504e0 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 75120fcbacd9 to 1db56b0f2cfb 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: I055eb301ac49cdc9f05faec92d75f4372c5f423a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3935617 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.