commit | 3ccd5fc859795035b9d20ee2083df667bf0c7467 | [log] [tgz] |
---|---|---|
author | Yuanjun Huang <yuanjunh@google.com> | Tue Mar 22 01:28:01 2022 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 22 01:28:01 2022 |
tree | 423cecf4e180dac675d0612521b1530fa5862f4b | |
parent | 00b0587a66e6a99a39453085e9678a5b9a29bc45 [diff] |
[buildbucket] Fix an agent output update bug Dev env is panic due to input.experiments is not set when bbagent sending update requests for agent output. On server side, we don't need to check if cipd_installation experiment is there to decide whether to allow the update. BBagent already has this control. Bug:1297809 Change-Id: I521d130029bd9d05a96ae471b9747ea3bca66440 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3541045 Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Yuanjun Huang <yuanjunh@google.com>
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 uses the same flow as Chromium contributions.