| commit | 510ebdc8158a48cb4521f69098ce299f6f740709 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Tue Jul 19 14:22:24 2022 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 19 21:31:13 2022 +0000 |
| tree | ca2e5e8167bf8fd892845c5e81977642c5275570 | |
| parent | b09b0c6de83be76b42a625f2f3a0b9bfd583fea6 [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/8808176138138575041 recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/a53cb2cf417da7ec0419cc283e9813586c9eea6b a53cb2c (iannucci@chromium.org) [manual_roll] Allow manual_roll to work even when protoc breaks. 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: I14aeecfcc983dde80a6835dcb6de33e72efc698e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3774597 Commit-Queue: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: 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.