commit | b03befeff1d576cdd3264327b04718e936c22bfe | [log] [tgz] |
---|---|---|
author | Azizur Rahman <azrahman@google.com> | Sun May 08 21:31:25 2022 +0000 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 09 14:50:50 2022 +0000 |
tree | 537dfc9872cbea12c217355667d324084f3efb47 | |
parent | b69f1cd2c18db7384ec022aabf5ecdd9d197ff21 [diff] |
test_request: add new fields for CFT executions support added new field for container metadata url. it's cleaner to have a new field not affecting non-cft workflow. Moved run_via_cft from suite to params. it's cleaner for params to have this info and download the metadata before invoking test_runner. BUG=b:230909741 TEST=None Change-Id: I06fdd9135cd94818bbfb8b37a86c2e8f50aac84a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3633000 Commit-Queue: Jared Loucks <jaredloucks@google.com> Reviewed-by: Jared Loucks <jaredloucks@google.com> Auto-Submit: Azizur Rahman <azrahman@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.