| commit | 27169a6f25d10f2b025ece9646d0234de5cf9723 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Mon Oct 02 17:35:21 2023 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 03 00:43:01 2023 +0000 |
| tree | 397376ce218dcfd3640d28dc1b4df15aeec90d8b | |
| parent | 4f9f56943aa78a49934ea0b87a8d99f145137795 [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/8768301518798016369 recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/ba4a2a613de79a08536e87f235c9e95e75e62702 ba4a2a6 (gregorynisbet@google.com) [recipes] Add validation for sub_build API 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: I81931ba74d1a5711ef7491287d62a85b1fa9804d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4908829 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.