commit | 7e880a487ad7f79161ac0c98598070aef685f5d6 | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Tue Apr 26 23:06:31 2022 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 26 23:06:31 2022 |
tree | 5ab3cb30575ced98217253da3eec23ce576c3569 | |
parent | 47c413ef57757a74d56fd99b01dc10149ae2f89c [diff] |
[deploy] Add a field with commit details to Deployment. They are useful in the UI when showing the history of actuations. They can theoretically be fetched dynamically by the backend, but so far it didn't need direct access to the configs repo and I'd like to keep it this way. It is arguably simpler to just grab it on the builder side in the recipe. R=ddoman@chromium.org, iannucci@chromium.org BUG=1301023 Change-Id: If4561c0799a5f3468ed139767adfa33f5098ded2 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3606386 Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
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.