| commit | 81d8ec479620046edd531d2c7b309519f4f09137 | [log] [tgz] |
|---|---|---|
| author | Jeff Yoon <jeffyoon@google.com> | Tue Jan 05 18:33:53 2021 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 05 18:33:53 2021 |
| tree | 215e74e8ba95f3c7c38ed3679a8b9d50fc8e8048 | |
| parent | 1deca0388644110396152608047cb759e0509f51 [diff] |
Adding support for chain-of-custody signatures for upload files Files for upload can add chain-of-custody signatures using the 'verifiable_key_path' key. This string path will invoke cloudkms to create a .sig file for each file in the ArchiveData definition. The .sig file is to be uploaded next to the original file in gcs. This .sig file will also be bundled into the .zip or .tar.gz if that's the selected archive type. Change-Id: If42674653894885bfa67cce665795044c51a6cfc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2586006 Reviewed-by: Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Jeff Yoon <jeffyoon@google.com>
If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*), please take a look at the README for more information pertaining to recipes.
The preferred style is PEP8 with two-space indent; that is, the Chromium Python style. Functions use lowercase_with_underscores, with the exception of the special functions RunSteps and RunTests in recipes. Use yapf (git cl format --no-clang-format) to autoformat new code.