Google Git
Sign in
chromium / infra / luci / luci-go / 0a3363dd1cffd8fe2b6545216effe12c3cfe7f86
commit0a3363dd1cffd8fe2b6545216effe12c3cfe7f86[log] [tgz]
authorNodir Turakulov <nodir@google.com>Sat Mar 23 01:04:32 2019
committerCommit Bot <commit-bot@chromium.org>Sat Mar 23 01:04:32 2019
treec0fbc5b5f4686040b56dca311bc485b1669d216e
parentf4468d81cae04fb33bd593df85f62a7985b3bd23 [diff]
[milo] Do not assume build has task id

After https://chromium-review.googlesource.com/c/infra/infra/+/1531678/11
a build does not necessarily has a swarming task. It is created
asynchronously.

Display a task link only if task id is known.

R=hinoka@chromium.org

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