| commit | f4cbaa91dc2a1c8a79f77ce899b6505e4b49fd4f | [log] [tgz] |
|---|---|---|
| author | Nodir Turakulov <nodir@google.com> | Thu Nov 29 18:39:08 2018 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Nov 29 18:39:08 2018 |
| tree | 375a482825409500ada57bff8aecc8b1b99f05d4 | |
| parent | 2f37f58c54c9d3ba76f8c5f13b7e890a72e74f24 [diff] |
[buildbucket] Add recipe info to build proto Milo would like to provide a link to the recipe used for a build. Record the recipe cipd package and recipe name, coming from cr-buildbucket.cfg This info will end up in BQ available for analysis. This does not provide the source code location (buildbucket doesn't have it anyway), but we could attach source code info to the CIPD package instance. Then Milo could load that. Later we can also add requested/actual CIPD version. R=iannucci@chromium.org, vadimsh@chromium.org Bug: 909893 Change-Id: I56346cd6da15d9e5f16e1c1daa6f0f1a0eee28d9 Reviewed-on: https://chromium-review.googlesource.com/c/1354093 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Ryan Tseng <hinoka@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>
LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:
fetch infra cd infra/go eval `./env.py` cd src/go.chromium.org/luci
Contributing uses the same flow as Chromium contributions.