| commit | 0884c4d360ce21addd837c601c000edcb47b5a44 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Tue Sep 13 13:22:21 2022 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 13 20:30:20 2022 +0000 |
| tree | 728efdadb2f7503aa35efaf2e008e8bba7656840 | |
| parent | 70d4c84e1fee69bc8d2784b0004a33409daaa86b [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) into this repository. The build that created this CL was https://ci.chromium.org/b/8803106479813693025 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/b1237034fdb4606ed151f260fff04a7a3ddab9e3 b123703 (vapier@chromium.org) Update license boilerplate text in source code files 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: I125f8ad7a9c25ef56aad14c6a0cec2352cee43c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3891745 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.