| commit | f47843d7b3b489472eb0baf9c77ed2d2b8ca60f4 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Tue Jun 07 13:47:58 2022 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 07 20:58:04 2022 +0000 |
| tree | f1cffe2ed495f279dc615e18cd457c9a59dc16b8 | |
| parent | 94c12f58cde44eea5180789d0c5df048f8d0a10d [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/8811983727583453953 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/b32a0f097803b18e63a473ccc9d671c381173621 b32a0f0 (justinsuen@google.com) dut-attributes: define new TleSource attributes recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/51b3aed56d1ba5b0e8ac65f94c20b15513a5f87c 51b3aed (jkusuma@google.com) Update go.chromium.org/luci protos related to resultdb. More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: Ib02d25d8cf15eb8367db9cf01e1369b9722feab0 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3693849 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.