| commit | 3000bf43edfc8b220ba822311d24cbdfe46a0d72 | [log] [tgz] |
|---|---|---|
| author | Vadim Shtayura <vadimsh@chromium.org> | Fri Jan 11 19:59:15 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 11 19:59:15 2019 |
| tree | 449653a6dd93ff19b65f23253d38fd0473a0c9a9 | |
| parent | 4f9ab59fed2146929cd085c7946651bd2126e709 [diff] |
[lucicfg] Finish gitiles_poller(...) definition. I decided to omit 'triggering_policy' for it, since I've never seen custom polices used with pollers. Can be added later if needed. Also the validation rules are quite involved, so let the server do the thorough validation and only validate types in lucicfg. R=tandrii@chromium.org, nodir@chromium.org BUG=833946 Change-Id: Icc56c5a3f2073dce51b3ad859e454ea36bef5382 Reviewed-on: https://chromium-review.googlesource.com/c/1406423 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.