commit | e9bce3db8631151f20d0e17458cc0304b07989c4 | [log] [tgz] |
---|---|---|
author | Lizzy Presland <zland@google.com> | Tue Aug 23 23:34:11 2022 +0000 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Nov 04 19:18:45 2022 +0000 |
tree | 704d8f9c1dbd2ec8596181d559dffe76160dc9d3 | |
parent | 07236b9769e67aba5c5ba8aa8d1995866f1633f3 [diff] |
chromite: Remove plain failed_packages fields Since we've migrated relevant endpoints to using a FailedPackageData field and some time has passed, delete and reserve the fields. BUG=b:206514844 TEST=./generate --allow-breaking Change-Id: If8345f0041b087d8418b15f7c73d3f3215dcedfb Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3853041 Reviewed-by: Cindy Lin <xcl@google.com> Auto-Submit: Lizzy Presland <zland@google.com> Commit-Queue: Cindy Lin <xcl@google.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.