| commit | fd6fd6d261c07a02ce11180d9fa735e3536aef49 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Mon May 16 18:17:16 2022 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 17 01:26:05 2022 +0000 |
| tree | 4fd7a2039c35dbd854d2bb926f7c846e680eaf7d | |
| parent | 4c8fd6959ead8341dad74d1fcd3b6ba32de8e143 [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/8813959873882141953 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+log/6619a47ca864cc6cc718a31e54735bb6cbe6125a~..60c740f92d030f518dca0bd262bd4ccde83cb572 6619a47 (pceballos@google.com) Add touch slop distance hardware feature and use it to set the... 60c740f (rrangel@chromium.org) config: Add AC/DC support for resourced config recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/08c51a101973b784d4de8fc198a1632d46508400 08c51a1 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from c25db5a11beb to d3db74920e35 More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=juahurta@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: Ia1f06a9fc3e522b8817d7c8810f3dc84d3bef160 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3651413 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.