| commit | fdb9c3d8a17dbc507fe4faeacffdac26c5dd9498 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Sat Mar 18 05:52:14 2023 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Mar 18 05:59:48 2023 |
| tree | c343e61d9ff67c62837a5196d9599ee14c83f11f | |
| parent | 610a652909e31ec02870d61c1d0875ad43c03f2f [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/8786310183726851953 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/a50332108dbff18c8ef0f146f237057bb7851b24 a503321 (yupingso@chromium.org) Support chromeos-config property "ec-rw-image" recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/73b6fe3ba2e2c54d16521a8c74d6b7753ec19537 73b6fe3 (tikuta@chromium.org) swarming: update owners of recipe_modules 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: I0e2c2c214d4749e61a2827e01b65fd8ed84d9dcd Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4351171 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.