| commit | 10106a59f6f7abe347dd32ffe197ce355bf2935a | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Wed May 04 22:56:40 2022 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 04 23:05:19 2022 |
| tree | 09c875bff4ac62b591a207df7b02d8c64f47d9b0 | |
| parent | 6d994b592d2318c10da3fc361060d949765fb62f [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/8815055845171124177 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+log/e6b08254d5631a94a64ae66e8c134dee9ec26f98~..f5859b168bae2e2dc873994b3c3d699fd40886c2 e6b0825 (sammc@chromium.org) Install apm.ini files as part of topology-level cras config files. a949ebc (sammc@chromium.org) Add a config DesignId override to DesignId to dedupe software c... 00d230e (andrewlamb@chromium.org) plan.proto: Add VMTestPlan proto. f5859b1 (jiwan@chromium.org) nnpalm: Add nnpalm config recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/bb1fb5af7df7af67167321440d19dd855abc7518 bb1fb5a (iannucci@chromium.org) [python] Set warning for entire python module. More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=tbain@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: Id94da9a063b79845e808f2bbe6c9c5d861fd6004 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3627478 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.