Integrate with Milo rendering CLs |
|||
Issue descriptionMilo supports a Blame List feature for showing the CL’s in a build. This is currently used by Chrome builds (example <https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/Google%20Chrome%20Mac/565> see “All Changes”). To implement this, we need to export the same metadata from any builder that is performing a cherry-pick stage to include CL’s, as a start. Then, later, once we can determine the previous build, we should also add this metadata for all changes between the previous build and the current one. For example, for release builders or post-submit builders, we should show all of the changes that landed between the current build and the last one. The same should be done for firmware and factory builders.
,
Nov 13
,
Nov 15
To do this, one must populate the manifest.proto <https://chromium.googlesource.com/infra/luci/luci-go/+/HEAD/common/proto/srcman/manifest.proto#25> and export this information to LogDog. The LUCI team has indicated that they may added it to Buildbucket build proto.
,
Dec 19
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jclinton@chromium.org
, Nov 8