Google Git
Sign in
chromium / infra / luci / luci-go / 8aff5692c6234ddac4104420620284dd1610a8aa
commit8aff5692c6234ddac4104420620284dd1610a8aa[log] [tgz]
authornqmtuan <nqmtuan@google.com>Fri Aug 02 01:52:35 2024
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Aug 02 01:52:35 2024
treea6d293e051e62688064d2169b422e51593c04568
parent26aa4a6021bea6298cab5d90a27971b9ae6570ef [diff]
[ArtifactExporter] Increase artifact limit of chromeOS to 50MB

Given that:
- Other projects have a lot of artifacts > 5 MB
- We already have limit for invocation level, which is 5GB. (We introduced this artifact size limit before the invocation limit)

I don't see the need to enforce a 5MB limit for chromeOS artifact.

Increase this to 50MB first and see if this breaks anything. Later we can either:
- Lift this limit (i.e. only keep the invocation-limit), or
- Use the same limit for all projects,

Change-Id: I707c78d221db10b81efc48e397eedf8ea903fd12
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/5755384
Commit-Queue: Tuan Nguyen <nqmtuan@google.com>
Reviewed-by: Matthew Warton <mwarton@google.com>
2 files changed
tree: a6d293e051e62688064d2169b422e51593c04568
  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. source_index/
  37. standalone/
  38. starlark/
  39. swarming/
  40. teams/
  41. third_party/
  42. tokenserver/
  43. tools/
  44. tree_status/
  45. vpython/
  46. web/
  47. .gitallowed
  48. .gitattributes
  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. tools.go
  62. 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.