commit | ee0fce909c40785380d73c83ee1084ad072ba654 | [log] [tgz] |
---|---|---|
author | Nodir Turakulov <nodir@google.com> | Wed Dec 26 21:53:06 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Dec 26 21:53:06 2018 |
tree | b712a09238f56935b67789170df0d936e44475f0 | |
parent | ebac1c199ba95f0ee490c25e673a3e5f391ee8a2 [diff] |
[buildbucket] Make Builder message self-sufficient Move non-builder fields in Swarming config message to Builder message, such that Builder messages are self-sufficient. This is preparation for moving Builder definitions to separate entities. Bug: 917873 Change-Id: Ib2ef402cbc1c0606a5b6b21f6a5004b85bfdcff8 Reviewed-on: https://chromium-review.googlesource.com/c/1390977 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Reviewed-by: Vadim Shtayura <vadimsh@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.