| commit | 6d994b592d2318c10da3fc361060d949765fb62f | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Tue May 03 04:15:43 2022 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 03 04:28:18 2022 |
| tree | d1cf7b4e6c9b27388fab736b759c46e8d1560fa6 | |
| parent | 49ff1704176519f3581705b08278bbd18da4c0cc [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/8815216905204548465 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/1485a109889d6efe50cbe6bb8bdcd52847cc9fe8 1485a10 (xianuowang@chromium.org) proto: Add update_firmware flag in cros_provision related protos recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/82fb654d0e289ca7f72aa4e57fc437f4877d42e7 82fb654 (meiring@google.com) [recipes-py] Update ResultDB exoneration example to populate re... More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=ctmcnamara@chromium.org Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: Ie48a2f17b4fa76f4cb17fd3d371f63a2975caee0 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3622135 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.