[resultui] improve resultdb integration hint

1. Add ResultDB integration hints (with an option to hide it) to the
bottom of the test results tab.
2. Mention luci-eng@ in integration hints.
3. Do not display "no associated invocation" when the invocation ID is
not initialised yet.

R=nqmtuan@google.com, orodley@google.com

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