| commit | 6412589afd138bd60e5cf97d36f8ab9fcb783791 | [log] [tgz] |
|---|---|---|
| author | Michael Achenbach <machenbach@chromium.org> | Tue Oct 13 13:46:18 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 13 13:46:18 2020 |
| tree | 9a1b122245bddd162f80903b16abda3f78cdc8bb | |
| parent | 226147bc66889400cd3d70ef2edac4eeb306f7a1 [diff] |
[archive] Enable overwriting the build-config for clusterfuzz archives This adds a parameter to clusterfuzz archiving for specifying the build config, i.e. 'release' or 'debug'. This is used by the archiving script to qualify the google storage path. If not given (legacy), the build config is inferred from the build output directory, which is brittle as it can be an arbitrary location. Chromium used to put build output into directories ending in 'Release' or 'Debug', but e.g. V8 uniformly uses 'build' now. Bug: 1137528 Change-Id: Iad6b1d868336a40ad5d1cb09ea3e130d5262aa2a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2461810 Auto-Submit: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@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.