commit | 37b4f2fcc80cf8075860412039614792ba2e0d93 | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Fri Jan 18 21:31:58 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 18 21:31:58 2019 |
tree | eba9c87468ccadf25ee34432c49aeb83d3940d31 | |
parent | b4704333465f3ab240922b5ec58f761ef683002e [diff] |
[lucicfg] Add 'schedule' and 'triggering_policy' to core.builder(...). Also improve the documentation regarding how batching happens, i.e. how git commits transform into builds. This concludes cr-buildbucket.cfg and luci-scheduler.cfg portion of lucicfg. R=tandrii@chromium.org, nodir@chromium.org BUG=833946 Change-Id: I4d58104565ca04ad2e9aeb779d269f81bdf37a36 Reviewed-on: https://chromium-review.googlesource.com/c/1419286 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@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.