New issue
Advanced search Search tips

Issue 903367 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Feature

Blocking:
issue 901883
issue 903364


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

Integrate with Milo rendering CLs

Project Member Reported by jclinton@chromium.org, Nov 8

Issue description

Milo 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.

 
Blocking: 901883
Labels: Disable-Nags
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.
Cc: estaab@chromium.org

Sign in to add a comment