Google Git
Sign in
chromium / infra / luci / luci-go / d73d7389b3a465efd87530548d44211613089c0b
commitd73d7389b3a465efd87530548d44211613089c0b[log] [tgz]
authorYiwei Zhang <yiwzhang@google.com>Wed Nov 08 05:37:59 2023
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Nov 08 05:37:59 2023
treec7388cf08c5a8af924510bf457ea8c253930bcc3
parentcf26edc84fcf70ffd81e1549de64b2810b645da1 [diff]
cv: allow submitted CL to create full run

There seems to be some regression caused by my previous refactoring
CL[1]. I suspect the reason is that when a full run successfully
submit the CL. Run Manager may receive a CL update event and decide
it can no longer create the full run and causing confusing behavior like
this: https://luci-change-verifier.appspot.com/ui/run/infra/8923555303854-1-f5432e69db20dc12

[1]: https://crrev.com/c/5010088

R=ddoman

Bug: 1498987
Change-Id: I10fe433d5922b5edea4d4711ff4eb2560cc31c91
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5012132
Reviewed-by: Scott Lee <ddoman@chromium.org>
Auto-Submit: Yiwei Zhang <yiwzhang@google.com>
Commit-Queue: Scott Lee <ddoman@chromium.org>
1 file changed
tree: c7388cf08c5a8af924510bf457ea8c253930bcc3
  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. resultdb/
  33. scheduler/
  34. scripts/
  35. server/
  36. standalone/
  37. starlark/
  38. swarming/
  39. third_party/
  40. tokenserver/
  41. tools/
  42. tree_status/
  43. vpython/
  44. web/
  45. .gitallowed
  46. .gitattributes
  47. .gitignore
  48. .golangci.yml
  49. AUTHORS
  50. codereview.settings
  51. CONTRIBUTING.md
  52. CONTRIBUTORS
  53. go.mod
  54. go.sum
  55. LICENSE
  56. OWNERS
  57. PRESUBMIT.py
  58. README.md
  59. tools.go
  60. 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.