commit | 58a5de36d55ffe1ee2fded1f715175634b136c93 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Mon Apr 11 11:32:46 2022 -0700 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 11 18:42:45 2022 +0000 |
tree | b4906cd0de8324dc6c5063402f009c4b39509d92 | |
parent | a605af227e7879c147ca0c38ca7cfe37457ea16c [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/8817155933623407377 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/fa31ad2a5225dbffdbf2cf741813c5ccc9aa5935 fa31ad2 (sammc@chromium.org) Generate cellular transmit power prefs from cellular and proxim... recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/0f5f374af06ce6c30708b36fd2545668dff22ad7 0f5f374 (alexschulze@chromium.org) [cipd] Fix `instances` command with limit = 0 More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=bshai@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I42c0d4d1edbc49422e11f8440e0b2a08ec2936ee Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3582265 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.