| commit | 37aae9ddeff596f8ee2bcb6a442f7601dbd0587c | [log] [tgz] |
|---|---|---|
| author | Jack Rosenthal <jrosenth@chromium.org> | Thu Apr 11 19:22:00 2024 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 12 21:35:39 2024 |
| tree | e637a393f30af0fc21274ccb85066ce6b8c74d72 | |
| parent | b3d33725135c417f4ee4c074a8845c5f507a6115 [diff] |
api: sdk: Add unpin_sdk flag to Update With pinned SDKs, we want to skip SDK update under all scenarios except: 1. The toolchain was changed, and therefore we need to test a new toolchain. 2. We've specifically been asked to build SDK packages from source. 3. The builder is configured as a "SDK next" builder, in that, we want to continue to update_chroot on this builder to ensure new changes won't break the SDK builder. This adds a flag which handles scenario #3. The Build API logic on the branch can then decide with these flags whether an update should actually be conducted or not. BUG=b:323085827 TEST=regen Change-Id: I6616bc0955d3d605d92317bcebdc57a7731ccde9 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5448163 Commit-Queue: Jack Rosenthal <jrosenth@chromium.org> Reviewed-by: Lee Presland <zland@google.com> Auto-Submit: Jack Rosenthal <jrosenth@chromium.org>
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.