[buildbucket] Handle nil history options

Bug: 1042991
Change-Id: I512a66660e58ee3bbff735f93b1eac1cb58f254f
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/2864511
Reviewed-by: Scott Lee <ddoman@chromium.org>
Reviewed-by: Yuanjun Huang <yuanjunh@google.com>
Commit-Queue: smut <smut@google.com>
1 file changed
tree: 48b38407557b741ad7d2536c3c09962df8d15e0d
  1. .gitallowed
  2. .gitattributes
  3. .gitignore
  4. AUTHORS
  5. CONTRIBUTING.md
  6. CONTRIBUTORS
  7. LICENSE
  8. OWNERS
  9. PRESUBMIT.py
  10. README.md
  11. WATCHLISTS
  12. appengine/
  13. auth/
  14. buildbucket/
  15. casviewer/
  16. cipd/
  17. client/
  18. cmdrunner/
  19. codereview.settings
  20. common/
  21. config/
  22. cq/
  23. cv/
  24. dm/
  25. examples/
  26. gae/
  27. gce/
  28. grpc/
  29. hardcoded/
  30. led/
  31. logdog/
  32. luci_notify/
  33. lucicfg/
  34. lucictx/
  35. luciexe/
  36. machine-db/
  37. milo/
  38. mmutex/
  39. mp/
  40. resultdb/
  41. scheduler/
  42. server/
  43. starlark/
  44. swarming/
  45. tokenserver/
  46. tools/
  47. tumble/
  48. vpython/
  49. web/
README.md

luci-go: LUCI services and tools in Go

GoDoc

Installing

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

Contributing uses the same flow as Chromium contributions.