| commit | 666328259b5c0c8f9f7ce7bc383a639c6a2c7051 | [log] [tgz] |
|---|---|---|
| author | Jack Rosenthal <jrosenth@chromium.org> | Fri Apr 12 22:43:36 2024 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 12 23:15:05 2024 |
| tree | c170304d831af19e0c6e0a42051f097d4cf45021 | |
| parent | 4c042f469591e7ef0b0fdfd7480ec50dfd913bf9 [diff] |
builder_config: Add "sdknext" option to sdk_update configuration
We plan to stand up a few builders ${BOARD}-sdknext-cq, which will
differ from their non -sdknext counterparts by actually doing an SDK
update. These can be used to ensure that changes won't be likely to
cause issues with the SDK builder.
Non -sdknext builders will change in that
chromite.api.SdkService/Update will exit without doing anything at all.
BUG=b:323085827
TEST=regen
Change-Id: I8848ec9ba5ed67574c3937106a750218f525a86c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5450636
Commit-Queue: Jack Rosenthal <jrosenth@chromium.org>
Commit-Queue: Alex Klein <saklein@chromium.org>
Reviewed-by: Alex Klein <saklein@chromium.org>
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.