Google Git
Sign in
chromium / infra / luci / luci-go / 79ae53a6d602392dbd90372c7650b246cbef5aad
commit79ae53a6d602392dbd90372c7650b246cbef5aad[log] [tgz]
authorVadim Shtayura <vadimsh@chromium.org>Fri Feb 14 01:45:35 2025
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Feb 14 01:45:35 2025
treeb8a531b72909338666d3ae0ccd2126a2ecada4e6
parentbdd9f0776dc6b33c2789c30bc5ef93665e637de6 [diff]
[swarming] Implement `termination_task_id`.

It is set in the GetBot (and bot listing) responses, when:
  1. The bot is dead ("is_dead" is true).
  2. The bot was terminated in response to TerminateBot RPC.

It is NOT set if:
  1. The bot is alive (actively pinging the server).
  2. The bot terminated itself in response to SIGTERM (or in some
     other way not involving TerminateBot).
  3. The bot just disappeared (stopped pinging the server).
  4. The bot reconnected after being terminated, and then died
     again for any reason other than (another) TerminateBot RPC.

`termination_task_id` is set to the task ID as returned by
TerminateBot RPC.

R=chanli@chromium.org
BUG=b/395973590

Change-Id: Ie00c845e6f9b5e09b390e3f3528a9ca3e11bab6d
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/6266869
Reviewed-by: Chan Li <chanli@chromium.org>
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
9 files changed
tree: b8a531b72909338666d3ae0ccd2126a2ecada4e6
  1. analysis/
  2. appengine/
  3. auth/
  4. auth_service/
  5. bisection/
  6. build/
  7. buildbucket/
  8. casviewer/
  9. cipd/
  10. cipkg/
  11. client/
  12. common/
  13. config/
  14. config_service/
  15. cv/
  16. deploy/
  17. examples/
  18. gae/
  19. gce/
  20. grpc/
  21. hardcoded/
  22. led/
  23. logdog/
  24. luci_notify/
  25. lucicfg/
  26. lucictx/
  27. luciexe/
  28. mailer/
  29. milo/
  30. mmutex/
  31. provenance/
  32. recipes_py/
  33. resultdb/
  34. scheduler/
  35. scripts/
  36. server/
  37. source_index/
  38. standalone/
  39. starlark/
  40. swarming/
  41. teams/
  42. third_party/
  43. tokenserver/
  44. tools/
  45. tree_status/
  46. vpython/
  47. web/
  48. .gitallowed
  49. .gitignore
  50. .go-lintable
  51. AUTHORS
  52. codereview.settings
  53. CONTRIBUTING.md
  54. CONTRIBUTORS
  55. go.mod
  56. go.sum
  57. LICENSE
  58. OWNERS
  59. PRESUBMIT.py
  60. README.md
  61. staticcheck.conf
  62. tools.go
  63. WATCHLISTS
README.md

luci-go: LUCI services and tools in Go

GoReference

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

It is now possible to directly install tools with go install:

go install go.chromium.org/luci/auth/client/cmd/...@latest
go install go.chromium.org/luci/buildbucket/cmd/...@latest
go install go.chromium.org/luci/cipd/client/cmd/...@latest
go install go.chromium.org/luci/client/cmd/...@latest
go install go.chromium.org/luci/cv/cmd/...@latest
go install go.chromium.org/luci/gce/cmd/...@latest
go install go.chromium.org/luci/grpc/cmd/...@latest
go install go.chromium.org/luci/logdog/client/cmd/...@latest
go install go.chromium.org/luci/luci_notify/cmd/...@latest
go install go.chromium.org/luci/lucicfg/cmd/...@latest
go install go.chromium.org/luci/luciexe/legacy/cmd/...@latest
go install go.chromium.org/luci/mailer/cmd/...@latest
go install go.chromium.org/luci/mmutex/cmd/...@latest
go install go.chromium.org/luci/resultdb/cmd/...@latest
go install go.chromium.org/luci/server/cmd/...@latest
go install go.chromium.org/luci/swarming/cmd/...@latest
go install go.chromium.org/luci/tokenserver/cmd/...@latest
go install go.chromium.org/luci/tools/cmd/...@latest

Contributing

Contributing uses the same flow as Chromium contributions.