commit | 0aa5d1476e3565959eaaa3549f6a89a19762271d | [log] [tgz] |
---|---|---|
author | Andrii Shyshkalov <tandrii@google.com> | Tue Sep 28 20:05:28 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 28 20:05:28 2021 |
tree | 0aa5a555e9a160fc338f3fc3c62b32bfa93293d8 | |
parent | 3176552177d539e4d3608f19cb9686eedc1d68a7 [diff] |
[cv][api] introduce run.CLQueryBuilder. Using raw Datastore keys on Run IDs proved very complicated for my brain, so I decided to encapsulate & test it well. So, Min .. Max do what one would expect on strings. And .After() and .Before() are introduced for ordering based on created time, but limited to specific LUCI project. R=robertocn, yiwzhang Change-Id: Ib430e792d0073a22f0a53a88e18255b0b1ea5084 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3182965 Auto-Submit: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com> Reviewed-by: Roberto Carrillo <robertocn@chromium.org> Reviewed-by: Yiwei Zhang <yiwzhang@google.com>
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.