commit | 58494f87c38b0fad812b1dde76ccbb62812dab54 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Thu Mar 24 12:25:06 2022 -0700 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 24 19:37:43 2022 +0000 |
tree | 1084c8f700f8b36b9108d756d6d06965d4dff421 | |
parent | cea52722a621a3b54ce31632787072a8f51702cf [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8818783532512959665 recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/826d446ec1118f691df2fa379d337e19aac3ea44 826d446 (kimstephanie@google.com) Add new post_process.PropertiesContain to check that key exists More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=jackneus@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: Ia1fdca84a55892527c6e4df7588c07431b8e68ca Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3550040 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.