[milo] Only show timeline for LUCI builds.

As part of the build.proto refactor, the timeline code will be increasingly
specific to build.proto.  To avoid maintaining two codepaths for timeline rendering,
we only want to support one, which is to show the timeline for LUCI builds only.

Also:
split tabs related CSS from timeline.css out to tabs.css

Change-Id: Ia3bd84e52a10c3972846c90a4917a394ffcab362
Reviewed-on: https://chromium-review.googlesource.com/c/1377050
Commit-Queue: Ryan Tseng <hinoka@chromium.org>
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
27 files changed
tree: 4ad3ef6044bffc575a64c43c6e691ae54cd207c2
  1. .travis.yml
  2. AUTHORS
  3. CONTRIBUTING.md
  4. CONTRIBUTORS
  5. LICENSE
  6. OWNERS
  7. PRESUBMIT.py
  8. README.md
  9. appengine/
  10. auth/
  11. buildbucket/
  12. cipd/
  13. client/
  14. codereview.settings
  15. common/
  16. config/
  17. dm/
  18. examples/
  19. gce/
  20. grpc/
  21. hardcoded/
  22. infra/
  23. logdog/
  24. luci_notify/
  25. lucicfg/
  26. lucictx/
  27. machine-db/
  28. milo/
  29. mmutex/
  30. mp/
  31. pre-commit-go.yml
  32. scheduler/
  33. scripts/
  34. server/
  35. starlark/
  36. tokenserver/
  37. tools/
  38. tumble/
  39. vpython/
  40. 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.